delete_twitter_watch
Delete a Twitter user from monitoring list.
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
Attacks that exploit this kind of access
The rule that runs delete_twitter_watch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Twitter MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_twitter_watch, this is the rule to start with:
delete_twitter_watch is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Twitter MCP Server, apply this rule, and every delete_twitter_watch call is checked against it from then on.
Questions about delete_twitter_watch
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.
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.
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.
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.
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.
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.
Across the catalogue