AI agents call mono_transactions to retrieve information from Monospay without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical transaction data without side effects. It queries existing records and returns information. The read-only designation and API key authentication confirm it poses no risk of data modification or financial loss. The low severity reflects that exposure of transaction history alone does not enable harmful actions, though it could leak account information depending on what data is included.
From the tool's definition Description explicitly states 'Fetch transaction history' and 'Read-only'. No modification, deletion, or execution capability described.
Attacks that exploit this kind of access
Fetch transaction history. Read-only, uses API key. It is categorised as a Read tool in the Monospay MCP Server, which means it retrieves data without modifying state.
Register the Monospay MCP server in PolicyLayer and add a rule for mono_transactions: 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 Monospay. Nothing to install.
mono_transactions 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 mono_transactions 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 mono_transactions. 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.
mono_transactions is provided by the Monospay MCP server (monospay/monospay). 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 →