AI agents call get_firm_user_mappings to retrieve information from Smokeball without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves organizational data (user mappings) without altering state. It is purely informational, similar to a directory lookup or list operation. The blast radius of misuse is minimal — exposing user mappings could constitute a data disclosure risk, but the tool itself performs no destructive, financial, or executable operations.
From the tool's definition Tool name and description indicate it 'List all user mappings for this firm' — a retrieval/query operation with no modification or side effects. No data is created, modified, deleted, or executed.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all user mappings for this firm. It is categorised as a Read tool in the Smokeball MCP Server, which means it retrieves data without modifying state.
Register the Smokeball MCP server in PolicyLayer and add a rule for get_firm_user_mappings: 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.
get_firm_user_mappings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_firm_user_mappings 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 get_firm_user_mappings. 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.
get_firm_user_mappings 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 →