delete_relation

Delete a relation by its ID. This removes the link between two database tables. Use list_database_relations to find relation IDs.

Server Fusebase MCP Server ryan-haver/fusebase-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_relation does on Fusebase MCP Server

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

Why delete_relation needs a policy

This tool permanently deletes database relationships, which cannot be easily undone. While not as severe as deleting entire tables or rows, removing relations between tables is destructive and could break data integrity or application functionality.

From the tool's definition The tool description explicitly states it will "Delete a relation" and "removes the link between two database tables." The verb "delete" combined with "removes" indicates irreversible removal of data relationships.

Questions about delete_relation

What does the delete_relation tool do? +

Delete a relation by its ID. This removes the link between two database tables. Use list_database_relations to find relation IDs. It is categorised as a Destructive tool in the Fusebase 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_relation? +

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

What risk level is delete_relation? +

delete_relation 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_relation? +

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

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

delete_relation is provided by the Fusebase MCP Server MCP server (ryan-haver/fusebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.