# get_spending_summary

Fetch a summary of the agent's spending to date.

Agent View of the PolicyLayer registry record for `get_spending_summary`. HTML page: https://policylayer.com/tools/advaitgore-agent-payment/get-spending-summary

## Facts

- Tool: `get_spending_summary`
- Server: AgentPay (`advaitgore/agent_payment`) — https://policylayer.com/tools/advaitgore-agent-payment.md
- Homepage: https://github.com/advaitgore/agent_payment
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_spending_summary",
    "arguments": {}
  }
}
```

## Why get_spending_summary is rated Low

This tool retrieves historical spending data for informational purposes only. It has no side effects, does not modify or delete data, does not execute transactions, and does not commit financial obligations. It is a straightforward read operation on an audit trail. Blast radius is minimal — at worst, an agent could access spending summaries it shouldn't, but no funds are at risk from the tool itself.

From the tool's own definition: "Tool name is 'get_spending_summary' and description states 'Fetch a summary of the agent's spending to date' — uses action verb 'Fetch' which retrieves data without modification."

## Use case

AI agents call get_spending_summary 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches AgentPay:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_spending_summary": {}
  }
}
```

## Other tools on AgentPay (8)

- `authorize_purchase` — Financial — https://policylayer.com/tools/advaitgore-agent-payment/authorize-purchase.md
- `create_account` — Financial — https://policylayer.com/tools/advaitgore-agent-payment/create-account.md
- `create_mandate` — Financial — https://policylayer.com/tools/advaitgore-agent-payment/create-mandate.md
- `update_mandate` — Financial — https://policylayer.com/tools/advaitgore-agent-payment/update-mandate.md
- `get_audit_log` — Read — https://policylayer.com/tools/advaitgore-agent-payment/get-audit-log.md
- `get_mandate` — Read — https://policylayer.com/tools/advaitgore-agent-payment/get-mandate.md
- `create_agent` — Write — https://policylayer.com/tools/advaitgore-agent-payment/create-agent.md
- `rotate_agent_key` — Write — https://policylayer.com/tools/advaitgore-agent-payment/rotate-agent-key.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=advaitgore-agent-payment · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/advaitgore-agent-payment