Validate that a read plan produced the expected cross-schema resolution.
AI agents call validate_read_plan to retrieve information from Weclapp Api Knowledge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs verification and inspection of read plans and schema resolution without creating, modifying, deleting, or executing operations. It is purely a validation/checking function that queries knowledge about API data structures, making it a Read category tool with low risk.
From the tool's definition Tool name 'validate_read_plan' and description 'Validate that a read plan produced the expected cross-schema resolution' indicate inspection and verification of data structures, not modification or execution.
Attacks that exploit this kind of access
Validate that a read plan produced the expected cross-schema resolution. It is categorised as a Read tool in the Weclapp Api Knowledge MCP Server, which means it retrieves data without modifying state.
Register the Weclapp Api Knowledge MCP server in PolicyLayer and add a rule for validate_read_plan: 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 Weclapp Api Knowledge. Nothing to install.
validate_read_plan 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_read_plan 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_read_plan. 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_read_plan is provided by the Weclapp Api Knowledge MCP server (serenmind/weclapp-api-knowledgebase-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 →