update_engagement
Update a consulting engagement (status, dates, rates, etc.).
This record as markdown: /tools/app-businys-mcp-server/update-engagement.md
What update_engagement does on Businys
AI agents use update_engagement to create or update resources in Businys, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Businys environment.
Why update_engagement is rated Medium
This tool modifies consulting engagement records, which are reversible changes (can be updated again). It does not delete data (Destructive), execute arbitrary code (Execute), involve money movement (Financial), or perform reads only (Read).
From the tool's definition Tool description states 'Update a consulting engagement (status, dates, rates, etc.)' — the verb 'update' and the enumerated fields (status, dates, rates) indicate modification of existing business-critical data records.
Attacks that exploit this kind of access
The rule that runs update_engagement safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_engagement, this is the rule to start with:
update_engagement 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 Businys, apply this rule, and every update_engagement call is checked against it from then on.
Questions about update_engagement
Update a consulting engagement (status, dates, rates, etc.). It is categorised as a Write tool in the Businys MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Businys MCP server in PolicyLayer and add a rule for update_engagement: 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 Businys. Nothing to install.
update_engagement 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_engagement 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_engagement. 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_engagement is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue