New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_twitter_watch

Delete a Twitter user from monitoring list.

SERVERTwitter MCP Server SOURCE6551team/opentwitter-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/6551team-opentwitter-mcp/delete-twitter-watch.md

What delete_twitter_watch does on Twitter MCP Server

AI agents call delete_twitter_watch to permanently remove resources in Twitter MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_twitter_watch is rated Critical

This tool irreversibly removes a monitored Twitter user entry. While it doesn't delete external Twitter data, it destroys a configured monitoring record that would need to be manually re-added, making it a Destructive operation. Severity is medium since the blast radius is limited to loss of monitoring configuration rather than loss of critical data.

From the tool's definition 'Delete a Twitter user from monitoring list' — permanently removes a user from the watch/monitoring list

Questions about delete_twitter_watch

What does the delete_twitter_watch tool do? +

Delete a Twitter user from monitoring list. It is categorised as a Destructive tool in the Twitter MCP Server 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 delete_twitter_watch? +

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

What risk level is delete_twitter_watch? +

delete_twitter_watch 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 delete_twitter_watch? +

Yes. Add a rate_limit block to the delete_twitter_watch 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 delete_twitter_watch completely? +

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

delete_twitter_watch is provided by the Twitter MCP Server MCP server (6551team/opentwitter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Twitter MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Twitter MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.