AI agents call monobank-personal-statement to retrieve information from Monobank without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of historical transaction data. It has no side effects, cannot modify or delete data, and does not execute code or trigger external operations. The blast radius of misuse is limited to unauthorized access to financial transaction history, which is lower severity than actual account modifications or fund transfers.
From the tool's definition Tool description states it 'Returns a list of transactions' with no modification, deletion, or execution capability. It retrieves account statement data with a maximum 31-day range.
Attacks that exploit this kind of access
Returns a list of transactions for a Monobank account. Maximum range is 31 days per request.\n\nInputs:\n- accountId: account id from monobank-personal-client-info. Use. It is categorised as a Read tool in the Monobank MCP Server, which means it retrieves data without modifying state.
Register the Monobank MCP server in PolicyLayer and add a rule for monobank-personal-statement: 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 Monobank. Nothing to install.
monobank-personal-statement 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 monobank-personal-statement 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 monobank-personal-statement. 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.
monobank-personal-statement is provided by the Monobank MCP server (todesstoss/monobank-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 →