Find where a field appears in a response and whether it is nested or referenced.
AI agents call explain_data_location 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 queries API documentation or cached schema knowledge to locate field positions within response structures. It performs passive analysis of data layout without side effects, state changes, or external operations. The sibling tools (analyze_response_structure, explain_endpoint, explain_entity, etc.) reinforce this server's purpose as a knowledge/documentation explorer rather than an action executor.
From the tool's definition Tool description states it 'Find[s] where a field appears in a response' — a pure information retrieval operation with no modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
Find where a field appears in a response and whether it is nested or referenced. 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_data_location: 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_data_location 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_data_location 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_data_location. 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_data_location 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 →