remove_company_agreement
Delete a contract/license from a company by id.
This record as markdown: /tools/ai-featureboard-featureboard/remove-company-agreement.md
What remove_company_agreement does on FeatureBoard
AI agents call remove_company_agreement to permanently remove resources in FeatureBoard, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_company_agreement is rated Critical
This tool permanently removes contractual agreements, which cannot be easily recovered and represents loss of critical business data. While not causing direct financial loss like a Financial category tool, the destruction of contracts has serious business implications.
From the tool's definition The tool explicitly 'Delete[s] a contract/license from a company by id', which is an irreversible removal of data. The word 'Delete' directly matches the Destructive category definition.
Attacks that exploit this kind of access
The rule that runs remove_company_agreement safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_company_agreement, this is the rule to start with:
remove_company_agreement 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 FeatureBoard, apply this rule, and every remove_company_agreement call is checked against it from then on.
Questions about remove_company_agreement
Delete a contract/license from a company by id. It is categorised as a Destructive tool in the FeatureBoard MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for remove_company_agreement: 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 FeatureBoard. Nothing to install.
remove_company_agreement 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_company_agreement 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_company_agreement. 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_company_agreement is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
Across the catalogue