Update the business profile on the configured phone number. Supply only the fields you want to change.
AI agents use update_business_profile to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.
This tool creates or modifies data reversibly—it updates a business profile rather than creating it from scratch or destructively removing it. The severity is medium because misuse could alter business presentation, contact details, or operational settings, but changes are generally reversible via another update.
From the tool's definition Tool description states 'Update the business profile' with ability to modify fields, which constitutes data modification without deletion. The context of an AP2 (Agent-to-Agent Payment Protocol) server suggests this affects business account configuration.
Documented attack patterns abuse exactly the kind of access update_business_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for update_business_profile:
{
"version": "1",
"default": "deny",
"tools": {
"update_business_profile": {
"limits": [
{
"counter": "update_business_profile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_business_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.
Free to start. No card required.
Update the business profile on the configured phone number. Supply only the fields you want to change. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for update_business_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 Mcp Ap2. Nothing to install.
update_business_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_business_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_business_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_business_profile is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.