This record as markdown: /tools/app-businys-mcp-server/update-sub-profile.md
What update_sub_profile does on Businys
AI agents use update_sub_profile 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_sub_profile is rated Medium
This tool creates or modifies data reversibly, fitting the Write category. Severity is medium because updating profile information could affect business operations and data accuracy, but it is not irreversible (Destructive), does not execute arbitrary code (Execute), and involves no financial transactions.
From the tool's definition Tool name 'update_sub_profile' and description 'Update a sub-profile' indicate modification of existing data. Context of business management tools (clients, invoices, contracts) suggests this updates user or sub-account profile information.
Attacks that exploit this kind of access
The rule that runs update_sub_profile 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_sub_profile, this is the rule to start with:
update_sub_profile 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_sub_profile call is checked against it from then on.
Questions about update_sub_profile
Update a sub-profile. 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_sub_profile: 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_sub_profile 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_sub_profile 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_sub_profile. 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_sub_profile 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