Get the outgoing payment by payment id
AI agents call get-outgoing-payment to retrieve information from Phoenixd MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical information about an outgoing payment without modifying state, executing code, or moving funds. It is a read-only query operation with minimal blast radius—exposure would primarily affect confidentiality of payment history rather than security of assets or operations.
From the tool's definition Tool name 'get-outgoing-payment' and description 'Get the outgoing payment by payment id' indicate a retrieval operation that queries payment information by identifier.
Attacks that exploit this kind of access
Get the outgoing payment by payment id. It is categorised as a Read tool in the Phoenixd MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Phoenixd MCP Server MCP server in PolicyLayer and add a rule for get-outgoing-payment: 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 Phoenixd MCP Server. Nothing to install.
get-outgoing-payment 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-outgoing-payment 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-outgoing-payment. 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-outgoing-payment is provided by the Phoenixd MCP Server MCP server (sharmaz/phoenixd-mcp-server). 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 →