update_company_agreement
Update a company contract/license by id — e.g. extend a license (new expiresAt), change status (
This record as markdown: /tools/ai-featureboard-featureboard/update-company-agreement.md
What update_company_agreement does on FeatureBoard
AI agents use update_company_agreement to create or update resources in FeatureBoard, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureBoard environment.
Why update_company_agreement is rated Medium
This tool modifies existing company agreement records (contracts/licenses) reversibly—updating fields like expiration dates or status. These changes can be undone or corrected with subsequent updates, so it does not qualify as Destructive.
From the tool's definition Tool name and description: 'Update a company contract/license by id — e.g. extend a license (new expiresAt), change status'. The word 'Update' and examples like 'extend a license' and 'change status' indicate modification of existing data.
Attacks that exploit this kind of access
The rule that runs update_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 update_company_agreement, this is the rule to start with:
update_company_agreement stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every update_company_agreement call is checked against it from then on.
Questions about update_company_agreement
Update a company contract/license by id — e.g. extend a license (new expiresAt), change status (. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for update_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.
update_company_agreement is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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.
This server
Across the catalogue