zernio_twitter_remove_bookmark
Remove a bookmarked tweet on a connected Twitter/X account.
This record as markdown: /tools/eyalm321-zernio-mcp/zernio-twitter-remove-bookmark.md
What zernio_twitter_remove_bookmark does on Zernio
AI agents call zernio_twitter_remove_bookmark to permanently remove resources in Zernio, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why zernio_twitter_remove_bookmark is rated Critical
Removing a bookmark is an irreversible deletion of a saved/bookmarked item. While it does not delete the tweet itself, it permanently removes the bookmark entry. The action cannot be undone through the API, making it Destructive rather than Write. Severity is medium since the blast radius is limited to loss of bookmarks, not content.
From the tool's definition Remove a bookmarked tweet on a connected Twitter/X account
Attacks that exploit this kind of access
The rule that runs zernio_twitter_remove_bookmark safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zernio, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zernio_twitter_remove_bookmark, this is the rule to start with:
zernio_twitter_remove_bookmark 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 Zernio, apply this rule, and every zernio_twitter_remove_bookmark call is checked against it from then on.
Questions about zernio_twitter_remove_bookmark
Remove a bookmarked tweet on a connected Twitter/X account. It is categorised as a Destructive tool in the Zernio MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zernio MCP server in PolicyLayer and add a rule for zernio_twitter_remove_bookmark: 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 Zernio. Nothing to install.
zernio_twitter_remove_bookmark 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 zernio_twitter_remove_bookmark 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 zernio_twitter_remove_bookmark. 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.
zernio_twitter_remove_bookmark is provided by the Zernio MCP server (eyalm321/zernio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zernio, and thousands of servers like it.
Across the catalogue