update_firm_user_mapping · Smokeball MCP: Risk & Policy

WHAT IT DOES

What update_firm_user_mapping does on Smokeball

AI agents use update_firm_user_mapping 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.

WHY IT NEEDS A POLICY

Why update_firm_user_mapping needs a policy

This tool modifies data (user mappings/permissions) reversibly—a staff member's system user link can be changed or removed without permanently destroying data. The operation falls under Write rather than Execute because it updates a configuration/mapping record rather than triggering arbitrary external actions.

From the tool's definition Tool name 'update_firm_user_mapping' and description 'Update a firm user mapping (link a staff member to a system user)' indicate a modification operation that creates or alters a mapping relationship between personnel and system access.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_firm_user_mapping Rate-limited

update_firm_user_mapping 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_firm_user_mapping": {
      "limits": [
        {
          "counter": "update_firm_user_mapping_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Smokeball, so you can run agents against it safely.

FAQ

Questions about update_firm_user_mapping

What does the update_firm_user_mapping tool do? +

Update a firm user mapping (link a staff member to a system user). 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.

How do I enforce a policy on update_firm_user_mapping? +

Register the Smokeball MCP server in PolicyLayer and add a rule for update_firm_user_mapping: 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.

What risk level is update_firm_user_mapping? +

update_firm_user_mapping is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_firm_user_mapping? +

Yes. Add a rate_limit block to the update_firm_user_mapping 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.

How do I block update_firm_user_mapping completely? +

Set action: deny in the PolicyLayer policy for update_firm_user_mapping. 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.

What MCP server provides update_firm_user_mapping? +

update_firm_user_mapping 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.