# Slash DGraph Lambdas Feature Requests / Small Change

**URL:** <https://discuss.dgraph.io/t/slash-dgraph-lambdas-feature-requests-small-change/13288>\
**Category:** Dgraph Cloud / Slash GraphQL\
**Tags:** slash-graphql, dgraph, kind:feature\
**Created:** [March 18, 2021, 10:17pm UTC](https://discuss.dgraph.io/t/slash-dgraph-lambdas-feature-requests-small-change/13288 "2021-03-18T22:17:45Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![jdgamble555](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/jdgamble555/32/7503_2.png) [@jdgamble555](https://discuss.dgraph.io/u/jdgamble555)\
**Post date:** [March 18, 2021, 10:17pm UTC](https://discuss.dgraph.io/t/slash-dgraph-lambdas-feature-requests-small-change/13288/1 "2021-03-18T22:17:45Z")

</div>

**Feature 1:** :

Get rid of the need for all auth rules in lambdas when calling **graphql**.

* * *

Just a few posts on the topic:

> [@Passing HTTP headers for @lambda](http://discuss.hypermode.com/t/passing-http-headers-for-lambda/11710/9):
>
> You can entirely bypass auth by making dql queries from lambda

> [@How do I protect certain fields with Slash GraphQL](http://discuss.hypermode.com/t/how-do-i-protect-certain-fields-with-slash-graphql/13148):
>
> HI All, I am new here. Last few days I spent a lot of time reading and watching videos about DGraph and Slash. I have a starter account setup on Slash and we are trying to get a POC rolling for a big project that we are developing. So my setup is that the Frontend is going to be connected to the Slash Graphql directly and there are no other middle servers. I am failing to understand a very basic question. Which is a very common usecase IMO, but I did not find anything on this, so I will ask …

* * *

I believe they are completely unnecessary. If I can call a regular **DQL** query, it is definitely not more secure. Simple is better. Hacking the auth rules and changing them is bad coding IMHO, and erroneous work for developers. If the lambda is called from a custom mutation, that custom mutation should have it’s own auth rules. Simple.

**Feature 2** :

This is probably the easiest fix. Allow **DQL** within lambdas to accept JSON Mutation Format. You could easily [update the code here](https://github.com/dgraph-io/dgraph-lambda/blob/8bb34dd627d0522fe8c0516cf784a5ecadc89523/src/dgraph.ts#L39).

My suggestion would be something as simple as:

```typescript
"Content-Type": typeof obj == 'object' ? "application/json" : "application/rdf"

```

It may be a little more complicated than that, but you get the drift.

Thanks,  
J

---

_[View the full topic](https://discuss.dgraph.io/t/slash-dgraph-lambdas-feature-requests-small-change/13288)._