AI agents call list_invoice_payments 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 and queries existing invoice payment records from the MyCase system. It accepts filter parameters but performs no side effects—it neither modifies data, executes operations, deletes records, nor moves money. The 'list' operation is a classic Read pattern with minimal risk if misused by an agent (worst case: exposure of payment history data already accessible to the authenticated user).
From the tool's definition Tool name 'list_invoice_payments' and description 'List invoice payments' indicate retrieval/query operation with filtering parameters (status, payable_id) but no modification or execution capability.
Attacks that exploit this kind of access
List invoice payments. status: pending|success|failure|error|timeout. payable_id: filter by invoice 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 list_invoice_payments: 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.
list_invoice_payments 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 list_invoice_payments 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 list_invoice_payments. 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.
list_invoice_payments 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 →