AI agents call get_firm to retrieve information from Mycase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves firm profile and configuration data without creating, modifying, deleting, or executing any actions. It is a read-only query operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_firm' and description 'Get this firm's profile and settings' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get this firm's profile and settings. It is categorised as a Read tool in the Mycase MCP Server, which means it retrieves data without modifying state.
Register the Mycase MCP server in PolicyLayer and add a rule for get_firm: 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 Mycase. Nothing to install.
get_firm 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 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. 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 is provided by the Mycase MCP server (rosenadvertising/mycase-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 →