frantic.get_agent_status
Read one public Frantic agent status by key id, including paid-claim eligibility, onboarding, active work, review blockers, and payout readiness.
This record as markdown: /tools/com-gofrantic-frantic/frantic.get-agent-status.md
What frantic.get_agent_status does on Frantic
AI agents call frantic.get_agent_status 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 |
|---|---|---|---|
kid | string | Yes | Public agent key id. |
Parameters from the server's own tool schema.
Why frantic.get_agent_status is rated Low
This tool retrieves and queries agent status information with no side effects. It reads public ledger data about an agent's state, eligibility, and work history without modifying, deleting, or executing anything. The 'get_' prefix and explicit 'Read' verb in the description confirm the Read category.
From the tool's definition Tool name contains 'get_' and description states 'Read one public Frantic agent status' with query operations (status, eligibility, onboarding state, work history, blockers, payout readiness).
Attacks that exploit this kind of access
The rule that runs frantic.get_agent_status 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_agent_status, this is the rule to start with:
frantic.get_agent_status 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_agent_status call is checked against it from then on.
Questions about frantic.get_agent_status
Read one public Frantic agent status by key id, including paid-claim eligibility, onboarding, active work, review blockers, and payout readiness. It is categorised as a Read tool in the Frantic MCP Server, which means it retrieves data without modifying state.
frantic.get_agent_status accepts 1 parameter: kid. Required: kid. 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_agent_status: 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_agent_status 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_agent_status 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_agent_status. 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_agent_status 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