This function marks resources cached on CDN nodes as expired. When users access these resources again, the CDN nodes will fetch the latest version from the origin server and store them anew.
AI agents invoke cdn_refresh to trigger actions in Qiniu MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external CDN operation — invalidating/expiring cached resources across CDN nodes. It doesn't delete data, but it executes a cache purge operation with side effects on CDN infrastructure. Misuse could cause a thundering herd effect (mass origin fetches) or serve stale/unintended content versions, making it Execute with medium severity.
From the tool's definition marks resources cached on CDN nodes as expired... CDN nodes will fetch the latest version from the origin server
Documented attack patterns abuse exactly the kind of access cdn_refresh gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qiniu MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cdn_refresh:
{
"version": "1",
"default": "deny",
"tools": {
"cdn_refresh": {
"limits": [
{
"counter": "cdn_refresh_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} cdn_refresh stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
This function marks resources cached on CDN nodes as expired. When users access these resources again, the CDN nodes will fetch the latest version from the origin server and store them anew. It is categorised as a Execute tool in the Qiniu MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Qiniu MCP Server MCP server in PolicyLayer and add a rule for cdn_refresh: 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 Qiniu MCP Server. Nothing to install.
cdn_refresh is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cdn_refresh 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 cdn_refresh. 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.
cdn_refresh is provided by the Qiniu MCP Server MCP server (qiniu/qiniu-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 Qiniu MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 Qiniu MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.