AI agents use utility_rename_sector to create or update resources in TdxQuant MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TdxQuant MCP Server environment.
The 'rename_sector' function modifies existing sector information irreversibly but preserves data (does not delete). This is categorized as Write rather than Destructive because renaming is typically reversible and doesn't destroy information. However, in a financial data context where sector names are critical identifiers, renaming could have downstream effects on market data integrity and trading operations.
From the tool's definition Tool name 'utility_rename_sector' indicates modification of sector data through a rename operation. Description is empty, limiting certainty.
Documented attack patterns abuse exactly the kind of access utility_rename_sector 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_rename_sector:
{
"version": "1",
"default": "deny",
"tools": {
"utility_rename_sector": {
"limits": [
{
"counter": "utility_rename_sector_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}utility_rename_sector 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.
utility_rename_sector. It is categorised as a Write tool in the TdxQuant MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TdxQuant MCP Server MCP server in PolicyLayer and add a rule for utility_rename_sector: 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_rename_sector 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 utility_rename_sector 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_rename_sector. 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_rename_sector 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.