# get_pricing

What a delivery costs, which packs exist, and the exact x402 payment requirements for each. Balance is counted in DELIVERIES, not money, and packs never expire. Call this before buying.

Agent View of the PolicyLayer registry record for `get_pricing`. HTML page: https://policylayer.com/tools/402cron/get-pricing

## Facts

- Tool: `get_pricing`
- Server: 402cron (`https://402cron.com/mcp`) — https://policylayer.com/tools/402cron.md
- Homepage: https://github.com/402cron/402cron
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- 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_pricing",
    "arguments": {}
  }
}
```

## Why get_pricing is rated Low

Even though get_pricing only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call get_pricing to retrieve information from 402cron 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 402cron:

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

## Other tools on 402cron (15)

- `delete_destination` — Destructive — https://policylayer.com/tools/402cron/delete-destination.md
- `delete_task` — Destructive — https://policylayer.com/tools/402cron/delete-task.md
- `run_task_now` — Execute — https://policylayer.com/tools/402cron/run-task-now.md
- `get_docs` — Read — https://policylayer.com/tools/402cron/get-docs.md
- `get_service_status` — Read — https://policylayer.com/tools/402cron/get-service-status.md
- `get_task` — Read — https://policylayer.com/tools/402cron/get-task.md
- `list_destinations` — Read — https://policylayer.com/tools/402cron/list-destinations.md
- `list_tasks` — Read — https://policylayer.com/tools/402cron/list-tasks.md
- `pause_task` — Read — https://policylayer.com/tools/402cron/pause-task.md
- `verify_destination` — Read — https://policylayer.com/tools/402cron/verify-destination.md
- `create_task` — Write — https://policylayer.com/tools/402cron/create-task.md
- `register_destination` — Write — https://policylayer.com/tools/402cron/register-destination.md
- `restore_task` — Write — https://policylayer.com/tools/402cron/restore-task.md
- `resume_task` — Write — https://policylayer.com/tools/402cron/resume-task.md
- `update_task` — Write — https://policylayer.com/tools/402cron/update-task.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=402cron · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/402cron
