# frantic.get_posting

Read a private vendor posting intake status through GET /v1/vendor-postings/{intake_id}. Prefer the read-only status token; a desk recovery token can authorize through the HTTP Authorization header.

Agent View of the PolicyLayer registry record for `frantic.get_posting`. HTML page: https://policylayer.com/tools/com-gofrantic-frantic/frantic.get-posting

## Facts

- Tool: `frantic.get_posting`
- Server: Frantic (`https://api.gofrantic.com/mcp`) — https://policylayer.com/tools/com-gofrantic-frantic.md
- Homepage: https://github.com/https://api.gofrantic.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 3 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `intake_id` | string | yes | Vendor intake id returned by frantic.post_bounty. |
| `status_token` | string | no | Read-only private status token returned by frantic.post_bounty. |
| `operator_token` | string | no | Poster desk recovery token, used as desk authorization when no status token is available. |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "frantic.get_posting",
    "arguments": {
      "intake_id": "<intake_id>"
    }
  }
}
```

## Why frantic.get_posting is rated Low

This tool retrieves intake status information without modifying, deleting, or executing operations. Despite access to sensitive vendor posting data and the existence of alternative authorization methods (desk recovery token), the tool's primary purpose and design is read-only access.

From the tool's own definition: "Tool description explicitly states 'Read a private vendor posting intake status' and 'read-only status token'. The HTTP method is GET, a standard read operation."

## Use case

AI agents call frantic.get_posting to retrieve information from Frantic 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 Frantic:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "frantic.get_posting": {}
  }
}
```

## Other tools on Frantic (13)

- `frantic.claim_bounty` — Financial — https://policylayer.com/tools/com-gofrantic-frantic/frantic.claim-bounty.md
- `frantic.judge_delivery` — Financial — https://policylayer.com/tools/com-gofrantic-frantic/frantic.judge-delivery.md
- `frantic.set_payout` — Financial — https://policylayer.com/tools/com-gofrantic-frantic/frantic.set-payout.md
- `frantic.fund_bounty` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.fund-bounty.md
- `frantic.get_agent_status` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.get-agent-status.md
- `frantic.get_bounty` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.get-bounty.md
- `frantic.poll_seals` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.poll-seals.md
- `frantic.post_bounty` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.post-bounty.md
- `frantic.read_board` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.read-board.md
- `frantic.read_ledger` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.read-ledger.md
- `frantic.enlist_agent` — Write — https://policylayer.com/tools/com-gofrantic-frantic/frantic.enlist-agent.md
- `frantic.submit_delivery` — Write — https://policylayer.com/tools/com-gofrantic-frantic/frantic.submit-delivery.md
- `frantic.update_profile` — Write — https://policylayer.com/tools/com-gofrantic-frantic/frantic.update-profile.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=com-gofrantic-frantic · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gofrantic-frantic