birst_delete_join

Delete a join (relationship) between two sources in a Birst space. Requires specifying the exact join properties to identify which join to delete.

Server Infor Birst MCP Server mikahdev/infor-birst-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What birst_delete_join does on Infor Birst MCP Server

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

Why birst_delete_join needs a policy

This tool permanently removes join definitions that establish relationships between data sources. While not as immediately catastrophic as deleting entire tables, removing joins breaks data model integrity and cannot be easily undone without administrative recovery or recreation of the join logic.

From the tool's definition The tool name explicitly contains 'delete' and the description states it 'Delete[s] a join (relationship) between two sources in a Birst space.' Deletion of database schema elements (joins/relationships) is irreversible structural modification.

Questions about birst_delete_join

What does the birst_delete_join tool do? +

Delete a join (relationship) between two sources in a Birst space. Requires specifying the exact join properties to identify which join to delete. It is categorised as a Destructive tool in the Infor Birst 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 birst_delete_join? +

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

What risk level is birst_delete_join? +

birst_delete_join 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 birst_delete_join? +

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

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

birst_delete_join is provided by the Infor Birst MCP Server MCP server (mikahdev/infor-birst-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.