Delete a keyword watchlist and all its tracked data.
AI agents call delete_keyword_watchlist to permanently remove resources in Outx — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (watchlist and tracked data) with no undo capability. Deletion operations fall into the Destructive category. The severity is high because inadvertent deletion could permanently lose monitoring data that may be important for business intelligence or compliance purposes. Confidence is high due to explicit 'delete' language in both name and description.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a keyword watchlist and all its tracked data.' The phrase 'all its tracked data' indicates irreversible removal of potentially valuable historical data.
Attacks that exploit this kind of access
Delete a keyword watchlist and all its tracked data. It is categorised as a Destructive tool in the Outx MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Outx MCP server in PolicyLayer and add a rule for delete_keyword_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 Outx. Nothing to install.
delete_keyword_watchlist 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_keyword_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.
Set action: deny in the PolicyLayer policy for delete_keyword_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.
delete_keyword_watchlist is provided by the Outx MCP server (outx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →