AI agents call check_response_consistency to retrieve information from Apifox MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only check/audit operation that examines API response formats for consistency. It retrieves and analyzes data without side effects, aligning with the 'Read' category. The operation is informational and diagnostic in nature, posing minimal risk if misused by an AI agent.
From the tool's definition Tool name 'check_response_consistency' and description '检查所有 API 的响应格式是否统一' (check if response formats of all APIs are unified) indicate inspection/validation of existing API responses with no modification, creation, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access check_response_consistency gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apifox MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_response_consistency:
{
"version": "1",
"default": "deny",
"tools": {
"check_response_consistency": {}
}
}check_response_consistency is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
检查所有 API 的响应格式是否统一。. It is categorised as a Read tool in the Apifox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Apifox MCP Server MCP server in PolicyLayer and add a rule for check_response_consistency: 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 Apifox MCP Server. Nothing to install.
check_response_consistency 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_response_consistency 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_response_consistency. 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_response_consistency is provided by the Apifox MCP Server MCP server (iwen-conf/apifox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apifox MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Apifox MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.