AI agents call utility_refresh_cache as a supporting operation in TdxQuant MCP Server workflows.
The tool name suggests it refreshes a cache, which is a utility/maintenance operation. Without a description, it's unclear whether this has side effects beyond invalidating and repopulating cached data. Cache refresh is typically a benign write-like operation with low blast radius. Confidence is low due to empty description.
From the tool's definition Tool name is 'utility_refresh_cache'; description is empty or uninformative.
Documented attack patterns abuse exactly the kind of access utility_refresh_cache gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TdxQuant MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for utility_refresh_cache:
{
"version": "1",
"default": "deny",
"tools": {
"utility_refresh_cache": {
"limits": [
{
"counter": "utility_refresh_cache_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} utility_refresh_cache gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
utility_refresh_cache. It is categorised as a Other tool in the TdxQuant MCP Server MCP Server, which means it performs auxiliary operations.
Register the TdxQuant MCP Server MCP server in PolicyLayer and add a rule for utility_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 TdxQuant MCP Server. Nothing to install.
utility_refresh_cache is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the utility_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 utility_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.
utility_refresh_cache is provided by the TdxQuant MCP Server MCP server (lingfan/tdxquant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TdxQuant 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.
39 TdxQuant MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.