Remove a specific edge by id.
AI agents call remove_edge to permanently remove resources in 247afk Block Editor MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing an edge from the graph is an irreversible deletion operation — it destroys a connection between nodes in the block editor without an undo mechanism implied by the description. This falls under Destructive as graph edges, once removed, cannot be recovered without re-adding them manually.
From the tool's definition Remove a specific edge by id
Attacks that exploit this kind of access
Remove a specific edge by id. It is categorised as a Destructive tool in the 247afk Block Editor MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 247afk Block Editor MCP Server MCP server in PolicyLayer and add a rule for remove_edge: 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 247afk Block Editor MCP Server. Nothing to install.
remove_edge 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 remove_edge 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 remove_edge. 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.
remove_edge is provided by the 247afk Block Editor MCP Server MCP server (itzdaimy/247afk-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 →