AI agents call get_expense 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.
The tool retrieves or queries a specific expense record from the MyCase system. It has no side effects: it does not create, modify, delete, or execute operations. This is a straightforward read operation on existing data.
From the tool's definition Tool name is 'get_expense' and description states 'Get a specific expense entry by ID' — this is a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get a specific expense entry by ID. 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_expense: 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_expense 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_expense 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_expense. 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_expense 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 →