Critical Risk →

remove_from_watchlist

Remove tickers from your saved watchlist.

Part of the TickerDB server.

remove_from_watchlist can permanently delete data in TickerDB, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE TICKERDB →

Free to start. No card required.

AI agents may call remove_from_watchlist to permanently remove or destroy resources in TickerDB. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call remove_from_watchlist in a loop, permanently destroying resources in TickerDB. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_from_watchlist"
  ]
}

See the full TickerDB policy for all 11 tools.

Get this rule live on your own TickerDB server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TICKERDB →

View all 11 tools →

These attack patterns abuse exactly the kind of access remove_from_watchlist gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so remove_from_watchlist only ever does what you allow.

SECURE TICKERDB →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the remove_from_watchlist tool do? +

Remove tickers from your saved watchlist.. It is categorised as a Destructive tool in the TickerDB MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_from_watchlist? +

Register the TickerDB MCP server in PolicyLayer and add a rule for remove_from_watchlist: 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 TickerDB. Nothing to install.

What risk level is remove_from_watchlist? +

remove_from_watchlist is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_from_watchlist? +

Yes. Add a rate_limit block to the remove_from_watchlist 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.

How do I block remove_from_watchlist completely? +

Set action: deny in the PolicyLayer policy for remove_from_watchlist. 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.

What MCP server provides remove_from_watchlist? +

remove_from_watchlist is provided by the TickerDB MCP server (tickerdb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TickerDB tool call.

Deterministic rules across all 11 TickerDB tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.