Call this after writing or editing any non-trivial function, module, or API endpoint.
AI agents call validate_code to retrieve information from MarkdownLM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a knowledge base to verify code against standards and rules. It retrieves or checks information without modifying code, systems, or data. The side effect is informational feedback only. Although it may be called post-write, the tool itself performs read-only validation. Classification as Read is appropriate.
From the tool's definition Tool name 'validate_code' and description indicating it is called 'after writing or editing' to verify compliance against documented standards.
Documented attack patterns abuse exactly the kind of access validate_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MarkdownLM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for validate_code:
{
"version": "1",
"default": "deny",
"tools": {
"validate_code": {}
}
}validate_code 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.
Call this after writing or editing any non-trivial function, module, or API endpoint. It is categorised as a Read tool in the MarkdownLM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MarkdownLM MCP Server MCP server in PolicyLayer and add a rule for validate_code: 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 MarkdownLM MCP Server. Nothing to install.
validate_code 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 validate_code 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 validate_code. 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.
validate_code is provided by the MarkdownLM MCP Server MCP server (markdownlm/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MarkdownLM MCP 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.
3 MarkdownLM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.