sign_contract
Sign a contract as the photographer. Adds the photographer
This record as markdown: /tools/app-businys-mcp-server/sign-contract.md
What sign_contract does on Businys
AI agents use sign_contract 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 sign_contract is rated Medium
Signing a contract creates a legally binding commitment on behalf of the user. While it is technically a write operation (adding a signature/record), it carries high severity because it creates legal obligations that may be difficult or impossible to reverse. It does not move money directly, so Financial is not the primary category, but misuse could lead to unintended legal agreements.
From the tool's definition "Sign a contract as the photographer. Adds the photographer"
Attacks that exploit this kind of access
The rule that runs sign_contract 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 sign_contract, this is the rule to start with:
sign_contract 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 sign_contract call is checked against it from then on.
Questions about sign_contract
Sign a contract as the photographer. Adds the photographer. 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 sign_contract: 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.
sign_contract 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 sign_contract 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 sign_contract. 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.
sign_contract 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