Get relevant context for current work
AI agents call get_context to retrieve information from Smart Code Search MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves context information to support development work. It has no described side effects, does not execute code, does not modify data, and does not delete anything. The blast radius of providing contextual information to an AI agent is minimal—it can only inform decisions, not cause harm directly.
From the tool's definition Tool name 'get_context' and description 'Get relevant context for current work' indicate a retrieval operation. The server provides 'semantic code search' and 'symbol analysis' capabilities without mentioning modification or execution of code.
Attacks that exploit this kind of access
Get relevant context for current work. It is categorised as a Read tool in the Smart Code Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Smart Code Search MCP 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 Smart Code Search MCP 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 Smart Code Search MCP Server MCP server (stevenjjobson/scs-mcp). 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 →