Get the current context and responses for a user
AI agents call get_context to retrieve information from Memory Context Provider Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries stored conversation context and returns it to the caller. It is a straightforward read operation that retrieves data without modifying, deleting, or executing any actions. The severity is low because retrieving stored context poses minimal risk, though access control should still be considered to prevent unauthorized context retrieval between users.
From the tool's definition Tool name is 'get_context' and description states it retrieves 'the current context and responses for a user' — a data retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the current context and responses for a user. It is categorised as a Read tool in the Memory Context Provider Server MCP Server, which means it retrieves data without modifying state.
Register the Memory Context Provider Server MCP server in PolicyLayer and add a rule for get_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 Memory Context Provider Server. Nothing to install.
get_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_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_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_context is provided by the Memory Context Provider Server MCP server (srish-ty/mcp-testing-interface-for-llms). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →