pay_status
Check wallet balance and status. Shows USDC balance, open tab count,
This record as markdown: /tools/io-github-pay-skill-pay-mcp/pay-status.md
What pay_status does on Pay Mcp
AI agents call pay_status to retrieve information from Pay Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pay_status is rated Low
This tool queries wallet information and account status without modifying, creating, deleting, or executing anything. It has no financial transaction capability (no transfers or charges), making it a straightforward Read operation with minimal risk if misused by an agent.
From the tool's definition Tool name 'pay_status' and description 'Check wallet balance and status. Shows USDC balance, open tab count' indicate data retrieval operations only. Verbs are 'check' and 'show', which are read-only queries without side effects.
Attacks that exploit this kind of access
The rule that runs pay_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pay Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pay_status, this is the rule to start with:
pay_status 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 Pay Mcp, apply this rule, and every pay_status call is checked against it from then on.
Questions about pay_status
Check wallet balance and status. Shows USDC balance, open tab count,. It is categorised as a Read tool in the Pay Mcp MCP Server, which means it retrieves data without modifying state.
Register the Pay MCP server in PolicyLayer and add a rule for pay_status: 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 Pay Mcp. Nothing to install.
pay_status 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 pay_status 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 pay_status. 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.
pay_status is provided by the Pay MCP server (@pay-skill/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pay, and thousands of servers like it.
This server
Across the catalogue