get_cc_history
Get your CC transaction history. All amounts returned in cogs (integer) and cc (display). 1 CC = 10,000 cogs. No api_key required.
This record as markdown: /tools/io-github-wirternow-agent-bank/get-cc-history.md
What get_cc_history does on Ai Agent Bank
AI agents call get_cc_history to retrieve information from Ai Agent Bank without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max results (default 50) |
agent_id | string | Yes | UUID of the agent |
Parameters from the server's own tool schema.
Why get_cc_history is rated Low
This tool retrieves and queries past transaction data without modifying, deleting, or executing any operations. It is a straightforward read operation that returns historical CC transaction records. While it exists within a financial infrastructure server, the tool itself only reads data; it does not move money, create obligations, or perform financial transactions.
From the tool's definition Tool description states 'Get your CC transaction history' — a retrieval operation with 'No api_key required' and 'No side effects' implied by read-only access to historical data.
Attacks that exploit this kind of access
The rule that runs get_cc_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ai Agent Bank, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_cc_history, this is the rule to start with:
get_cc_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ai Agent Bank, apply this rule, and every get_cc_history call is checked against it from then on.
Questions about get_cc_history
Get your CC transaction history. All amounts returned in cogs (integer) and cc (display). 1 CC = 10,000 cogs. No api_key required. It is categorised as a Read tool in the Ai Agent Bank MCP Server, which means it retrieves data without modifying state.
get_cc_history accepts 2 parameters: limit, agent_id. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the Ai Agent Bank MCP server in PolicyLayer and add a rule for get_cc_history: 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 Ai Agent Bank. Nothing to install.
get_cc_history 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_cc_history 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_cc_history. 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_cc_history is provided by the Ai Agent Bank MCP server (https://tdueqhfxyojmjgactdyc.supabase.co/functions/v1/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ai Agent Bank, and thousands of servers like it.
This server
Across the catalogue