Check whether a field path exists in OpenAPI and optionally in a live payload.
AI agents call check_field_presence 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 read-only introspection of API schema (OpenAPI) and optionally retrieves and inspects a live payload to verify field presence. It has no side effects, does not modify data, does not execute arbitrary operations, and does not trigger external actions beyond safe GET requests for inspection purposes. It falls squarely into the Read category.
From the tool's definition Tool name is 'check_field_presence' and description states it checks 'whether a field path exists in OpenAPI and optionally in a live payload.' The verbs are 'check' and 'exists'—purely informational queries with no modification, deletion, or execution of…
Attacks that exploit this kind of access
Check whether a field path exists in OpenAPI and optionally in a live payload. 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 check_field_presence: 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.
check_field_presence 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 check_field_presence 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 check_field_presence. 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.
check_field_presence 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 →