Get all stored user context values. Returns the persistent key-value store that accumulates across multiple show_input_form calls with keys.
AI agents call get_user_context to retrieve information from Pane without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries stored context data without creating, modifying, deleting, or executing any operations. It has no side effects beyond returning information. The persistent key-value store is accessed but not altered.
From the tool's definition The tool name is 'get_user_context' and the description states it 'Get all stored user context values' and 'Returns the persistent key-value store'. The verb 'Get' and 'Returns' indicate a read-only retrieval operation with no modification of underlying data.
Documented attack patterns abuse exactly the kind of access get_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 get_user_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_context": {}
}
}get_user_context is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all stored user context values. Returns the persistent key-value store that accumulates across multiple show_input_form calls with keys. It is categorised as a Read tool in the Pane MCP Server, which means it retrieves data without modifying state.
Register the Pane MCP server in PolicyLayer and add a rule for get_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.
get_user_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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.