Directly set a value in the user context without showing an input form. Useful for storing computed values or information gathered from conversation.
AI agents use set_user_context to create or update resources in Pane — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pane environment.
The tool creates or modifies context data (user context state) reversibly. It does not execute code, delete data, or transfer funds. However, it can alter application state that may affect subsequent interactions, warranting medium severity if misused by an agent to inject malicious values into a shared context.
From the tool's definition Tool description: 'Directly set a value in the user context' — this modifies stored state. The phrase 'storing computed values or information' confirms data persistence/mutation rather than retrieval.
Documented attack patterns abuse exactly the kind of access set_user_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pane, and nothing reaches the server without passing your rules. This is the rule we recommend for set_user_context:
{
"version": "1",
"default": "deny",
"tools": {
"set_user_context": {
"limits": [
{
"counter": "set_user_context_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_user_context 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.
Directly set a value in the user context without showing an input form. Useful for storing computed values or information gathered from conversation. It is categorised as a Write tool in the Pane MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pane MCP server in PolicyLayer and add a rule for set_user_context: 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 Pane. Nothing to install.
set_user_context 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_user_context 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_user_context. 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_user_context is provided by the Pane MCP server (zabaca/pane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pane, 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.
15 Pane tools catalogued and risk-classified — across an index of 43,000+ MCP servers.