Remove the time scrubber from a tool — return it to live mode.
AI agents use qd_reset_to_live to create or update resources in QuantData MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuantData MCP Server environment.
This tool modifies the state of a tool by removing a configuration (the time scrubber) and switching it to live mode. It changes a setting/configuration reversibly (the scrubber could presumably be re-added), making it a Write action. It doesn't delete data, execute code, or involve financial transactions.
From the tool's definition Remove the time scrubber from a tool — return it to live mode
Documented attack patterns abuse exactly the kind of access qd_reset_to_live gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QuantData MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for qd_reset_to_live:
{
"version": "1",
"default": "deny",
"tools": {
"qd_reset_to_live": {
"limits": [
{
"counter": "qd_reset_to_live_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} qd_reset_to_live 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.
Remove the time scrubber from a tool — return it to live mode. It is categorised as a Write tool in the QuantData MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the QuantData MCP Server MCP server in PolicyLayer and add a rule for qd_reset_to_live: 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 QuantData MCP Server. Nothing to install.
qd_reset_to_live 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 qd_reset_to_live 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 qd_reset_to_live. 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.
qd_reset_to_live is provided by the QuantData MCP Server MCP server (zzulanas/quantdata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from QuantData 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.
50 QuantData MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.