Use this when checking coding conventions before or during implementation.
AI agents call get_standards 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.
The tool retrieves coding standards and conventions from the engineering context synthesized by DevsContext. This is a pure read operation—it queries data to inform decision-making but produces no side effects, state changes, or irreversible actions. Low severity because misuse would at worst expose information the agent already has access to, with no ability to harm systems or data.
From the tool's definition Tool description: 'Use this when checking coding conventions before or during implementation.' This is a retrieval operation that fetches existing standards/conventions data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Use this when checking coding conventions before or during implementation. 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 get_standards: 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.
get_standards 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_standards 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_standards. 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_standards 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 →