get_status
Get your wallet status: balance, reputation tier, active escrows, open tabs, and streams.
This record as markdown: /tools/pay-skill-mcp/get-status.md
What get_status does on Remit Md MCP Server
AI agents call get_status to retrieve information from Remit Md MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_status is rated Low
This tool retrieves wallet and account metadata (balance, reputation, escrow status, tabs, streams) without creating, modifying, or deleting data. It has no side effects and poses minimal security risk even if misused by an agent, as it only exposes read-only financial visibility. Categorized as Read despite the financial context, as the tool itself performs no financial action.
From the tool's definition Tool name 'get_status' and description 'Get your wallet status: balance, reputation tier, active escrows, open tabs, and streams' indicate retrieval of account information with no modification or execution of transactions.
Attacks that exploit this kind of access
The rule that runs get_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Remit Md MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_status, this is the rule to start with:
get_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 Remit Md MCP Server, apply this rule, and every get_status call is checked against it from then on.
Questions about get_status
Get your wallet status: balance, reputation tier, active escrows, open tabs, and streams. It is categorised as a Read tool in the Remit Md MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Remit Md MCP Server MCP server in PolicyLayer and add a rule for get_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 Remit Md MCP Server. Nothing to install.
get_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 get_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 get_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.
get_status is provided by the Remit Md MCP Server 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 Remit Md MCP Server, and thousands of servers like it.
This server
Across the catalogue