AI agents call get_file_history 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 version history information about files associated with a matter in the Smokeball practice management system. It is a read operation that queries existing data without modifying, creating, deleting, or executing anything. The user impact of misuse is minimal—an agent could access historical file information it shouldn't see, but cannot alter or delete data.
From the tool's definition Tool name 'get_file_history' and description 'Get file version history for a matter' indicate a read-only retrieval operation. The verb 'get' and the action of retrieving historical data confirms this is a query operation with no side effects.
Attacks that exploit this kind of access
Get file version history for a matter. 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_file_history: 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_file_history 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_file_history 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_file_history. 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_file_history 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 →