Check an existing Metalsmith plugin against quality standards.
AI agents call validate to retrieve information from Metalsmith Plugin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The validate tool performs analysis and quality checks on an existing plugin. It retrieves and evaluates data against standards but does not create, modify, delete, or execute arbitrary code. The blast radius of misuse is minimal—an attacker could only gain insights into plugin quality metrics, not cause harm to systems or data.
From the tool's definition Tool name 'validate' and description 'Check an existing Metalsmith plugin against quality standards' indicate inspection/verification activity with no modifications, deletions, or external state changes.
Attacks that exploit this kind of access
Check an existing Metalsmith plugin against quality standards. It is categorised as a Read tool in the Metalsmith Plugin MCP Server, which means it retrieves data without modifying state.
Register the Metalsmith Plugin MCP server in PolicyLayer and add a rule for validate: 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 Metalsmith Plugin. Nothing to install.
validate 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 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. 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 is provided by the Metalsmith Plugin MCP server (metalsmith-plugin-mcp-server). 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 →