Run RunContext linter against the context graph and return diagnostics
AI agents call context_validate to retrieve information from RunContext without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis (linting) on a context graph to identify issues and return diagnostic information. It has no side effects—it reads and analyzes metadata without creating, modifying, deleting, or executing any operations on the database itself. The sibling tools (db_query, db_describe_table, etc.) reveal this server's broader purpose, but this specific tool is a read-only diagnostic utility.
From the tool's definition Tool name 'context_validate' and description 'Run RunContext linter against the context graph and return diagnostics' indicate a validation/linting operation that analyzes metadata and returns diagnostic results without modifying data or executing queries.
Attacks that exploit this kind of access
Run RunContext linter against the context graph and return diagnostics. It is categorised as a Read tool in the RunContext MCP Server, which means it retrieves data without modifying state.
Register the RunContext MCP server in PolicyLayer and add a rule for context_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 RunContext. Nothing to install.
context_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 context_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 context_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.
context_validate is provided by the RunContext MCP server (quiet-victory-labs/runcontext). 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 →