AI agents use set_access_token to create or update resources in Turtlestack Lite — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Turtlestack Lite environment.
This tool modifies system state by persisting authentication credentials, which is a Write operation. Severity is high because a compromised access token could enable unauthorized trading operations, portfolio access, or financial transactions on connected brokers (Kite, Groww, Dhan).
From the tool's definition Tool name 'set_access_token' and description 'Set access token after successful login' indicate modification of authentication state. The tool writes/stores credentials that enable subsequent API access to trading systems.
Documented attack patterns abuse exactly the kind of access set_access_token gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Turtlestack Lite, and nothing reaches the server without passing your rules. This is the rule we recommend for set_access_token:
{
"version": "1",
"default": "deny",
"tools": {
"set_access_token": {
"limits": [
{
"counter": "set_access_token_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_access_token stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set access token after successful login. It is categorised as a Write tool in the Turtlestack Lite MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Turtlestack Lite MCP server in PolicyLayer and add a rule for set_access_token: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Turtlestack Lite. Nothing to install.
set_access_token is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_access_token rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for set_access_token. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
set_access_token is provided by the Turtlestack Lite MCP server (turtlehq-tech/turtlestack-lite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Turtlestack Lite, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
45 Turtlestack Lite tools catalogued and risk-classified — across an index of 43,000+ MCP servers.