AI agents use update_contact_relation to create or update resources in Smokeball — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Smokeball environment.
This tool modifies relationship metadata (the type classification of an existing contact relationship) reversibly. It is a Write operation because it changes data state without permanently destroying it or executing arbitrary code.
From the tool's definition Tool name 'update_contact_relation' and description 'Update a contact relationship type' indicate modification of existing relationship data without irreversible deletion or financial impact.
Attacks that exploit this kind of access
Update a contact relationship type. It is categorised as a Write tool in the Smokeball MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Smokeball MCP server in PolicyLayer and add a rule for update_contact_relation: 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 Smokeball. Nothing to install.
update_contact_relation 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_contact_relation 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_contact_relation. 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_contact_relation is provided by the Smokeball MCP server (rosenadvertising/smokeball-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →