get_agent_status
Get detailed status for a specific agent: active/paused state, balance, strategy, today
This record as markdown: /tools/abcxz-conviction-fm/get-agent-status.md
What get_agent_status does on Conviction
AI agents call get_agent_status to retrieve information from Conviction without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_agent_status is rated Low
This tool retrieves and queries agent status data without creating, modifying, deleting, or executing any operations. It is a pure read operation that provides visibility into agent state and has no blast radius beyond information disclosure.
From the tool's definition Tool name is 'get_agent_status' and description states 'Get detailed status for a specific agent' — uses 'Get' verb indicating retrieval only. Returns state information (active/paused, balance, strategy, today) with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs get_agent_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Conviction, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_agent_status, this is the rule to start with:
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 Conviction, apply this rule, and every get_agent_status call is checked against it from then on.
Questions about get_agent_status
Get detailed status for a specific agent: active/paused state, balance, strategy, today. It is categorised as a Read tool in the Conviction MCP Server, which means it retrieves data without modifying state.
Register the Conviction MCP server in PolicyLayer and add a rule for 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 Conviction. Nothing to install.
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 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 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.
get_agent_status is provided by the Conviction MCP server (abcxz/conviction-fm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Conviction, and thousands of servers like it.
This server
Across the catalogue