Check project conventions and architecture rules
AI agents call check_conventions to retrieve information from MCP DevTools Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and analyzes existing project conventions and architecture rules to validate compliance. It retrieves information about the project structure and rules but does not execute code, modify files, delete data, or trigger external operations.
From the tool's definition Tool performs a 'Check' operation on project conventions and architecture rules, which is a read-only inspection activity with no modification or execution of code.
Documented attack patterns abuse exactly the kind of access check_conventions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP DevTools Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_conventions:
{
"version": "1",
"default": "deny",
"tools": {
"check_conventions": {}
}
}check_conventions 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.
Check project conventions and architecture rules. It is categorised as a Read tool in the MCP DevTools Server MCP Server, which means it retrieves data without modifying state.
Register the MCP DevTools Server MCP server in PolicyLayer and add a rule for check_conventions: 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 MCP DevTools Server. Nothing to install.
check_conventions 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 check_conventions 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 check_conventions. 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.
check_conventions is provided by the MCP DevTools Server MCP server (rshade/mcp-devtools-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP DevTools Server, 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.
79 MCP DevTools Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.