check_account
Check if the account is ready to make purchases. Call this BEFORE create_card to give proactive guidance.
This record as markdown: /tools/agentpay/check-account.md
What check_account does on Agentpay
AI agents call check_account to retrieve information from Agentpay without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_account is rated Low
This tool retrieves or queries account status information without modifying, deleting, or executing any operations. While the server handles financial systems, this specific tool only reads account state and provides guidance. It poses minimal risk if misused by an AI agent, as it cannot move money, create obligations, or alter data.
From the tool's definition Tool description states 'Check if the account is ready to make purchases' — a query operation with no side effects. The verb 'check' and the clarification to call it 'BEFORE create_card' indicate this is a read-only verification step.
Attacks that exploit this kind of access
The rule that runs check_account safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agentpay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_account, this is the rule to start with:
check_account 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 Agentpay, apply this rule, and every check_account call is checked against it from then on.
Questions about check_account
Check if the account is ready to make purchases. Call this BEFORE create_card to give proactive guidance. It is categorised as a Read tool in the Agentpay MCP Server, which means it retrieves data without modifying state.
Register the Agentpay MCP server in PolicyLayer and add a rule for check_account: 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 Agentpay. Nothing to install.
check_account 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 check_account 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 check_account. 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.
check_account is provided by the Agentpay MCP server (agentpay-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agentpay, and thousands of servers like it.
This server
Across the catalogue