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.
This record as markdown: /tools/com-gofrantic-frantic/frantic.get-posting.md
What frantic.get_posting does on Frantic
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
intake_id | string | Yes | Vendor intake id returned by frantic.post_bounty. |
status_token | string | — | Read-only private status token returned by frantic.post_bounty. |
operator_token | string | — | Poster desk recovery token, used as desk authorization when no status token is available. |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs frantic.get_posting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frantic, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For frantic.get_posting, this is the rule to start with:
frantic.get_posting 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 Frantic, apply this rule, and every frantic.get_posting call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Frantic MCP Server, which means it retrieves data without modifying state.
frantic.get_posting accepts 3 parameters: intake_id, status_token, operator_token. Required: intake_id. The full parameter table on this page comes from the server's own tool schema.
Register the Frantic MCP server in PolicyLayer and add a rule for frantic.get_posting: 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 Frantic. Nothing to install.
frantic.get_posting 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 frantic.get_posting 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 frantic.get_posting. 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.
frantic.get_posting is provided by the Frantic MCP server (https://api.gofrantic.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Frantic, and thousands of servers like it.
This server
Across the catalogue