Validate a context file and its referenced component files.
AI agents call validate-context to retrieve information from Context Compose without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs validation (inspection and checking) of context and component files. Validation is inherently a read operation with no side effects, no data modification, no code execution, and no irreversible actions. The lowest severity applies because misuse would only result in false positives/negatives during validation, not actual system changes.
From the tool's definition Tool name is 'validate-context' and description states it 'Validate a context file and its referenced component files' — validation is a read-only operation that checks syntax/structure without modifying or executing anything.
Attacks that exploit this kind of access
Validate a context file and its referenced component files. It is categorised as a Read tool in the Context Compose MCP Server, which means it retrieves data without modifying state.
Register the Context Compose MCP server in PolicyLayer and add a rule for validate-context: 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 Context Compose. Nothing to install.
validate-context 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-context 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-context. 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-context is provided by the Context Compose MCP server (lazylagom/context-compose-mcp). 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 →