Explain weclapp v2 filters, projection, includeReferencedEntities, and examples.
AI agents call explain_filter_syntax 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 is purely informational—it teaches users how to construct filter queries and use API parameters. It does not execute filters, modify data, or trigger operations. It belongs in the Read category with low severity because misuse merely provides incorrect learning, not harmful API calls.
From the tool's definition Tool name 'explain_filter_syntax' and description 'Explain weclapp v2 filters, projection, includeReferencedEntities, and examples' indicate the tool retrieves and presents documentation or explanatory information about API syntax.
Attacks that exploit this kind of access
Explain weclapp v2 filters, projection, includeReferencedEntities, and examples. 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 explain_filter_syntax: 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.
explain_filter_syntax 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 explain_filter_syntax 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 explain_filter_syntax. 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.
explain_filter_syntax 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 →