AI agents use refresh_cache to create or update resources in Apifox Filter MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apifox Filter MCP Server environment.
This tool refreshes/invalidates a cache and re-fetches data from Apifox. It modifies the cached state (a write operation) but does not delete or irreversibly destroy data. The blast radius is low since the worst outcome is stale cache being replaced with fresh data.
From the tool's definition 刷新接口缓存，从 Apifox 重新获取最新数据 (Refresh API cache, re-fetch latest data from Apifox)
Documented attack patterns abuse exactly the kind of access refresh_cache gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apifox Filter MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for refresh_cache:
{
"version": "1",
"default": "deny",
"tools": {
"refresh_cache": {
"limits": [
{
"counter": "refresh_cache_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}refresh_cache stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
刷新接口缓存，从 Apifox 重新获取最新数据. It is categorised as a Write tool in the Apifox Filter MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apifox Filter MCP Server MCP server in PolicyLayer and add a rule for refresh_cache: 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 Filter MCP Server. Nothing to install.
refresh_cache is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the refresh_cache 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 refresh_cache. 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.
refresh_cache is provided by the Apifox Filter MCP Server MCP server (xiaou66/apifox-filter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apifox Filter 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.
9 Apifox Filter MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.