Use this for freeform questions about the codebase, architecture,
AI agents call search_context to retrieve information from DevsContext without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing engineering context (requirements, decisions, architecture, standards) from Jira and Slack. It has no side effects—it only retrieves and presents synthesized information to help coding agents understand task requirements and codebase standards. No data is created, modified, deleted, or executed.
From the tool's definition Tool name 'search_context' and description 'Use this for freeform questions about the codebase, architecture' indicate retrieval of information. The server fetches and synthesizes relevant information on demand without modifying or executing changes.
Attacks that exploit this kind of access
Use this for freeform questions about the codebase, architecture,. It is categorised as a Read tool in the DevsContext MCP Server, which means it retrieves data without modifying state.
Register the DevsContext MCP server in PolicyLayer and add a rule for search_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 DevsContext. Nothing to install.
search_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 search_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 search_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.
search_context is provided by the DevsContext MCP server (pro0f/devscontext). 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 →