Get status information for agents in the system.
AI agents call get_agent_status to retrieve information from Sentient Brain Smithery without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns status information about agents. The verb 'get' combined with 'status information' indicates a read-only query operation. There is no indication of data modification, code execution, deletion, or financial operations. The low severity reflects that status information is typically non-sensitive operational metadata with minimal blast radius if misused.
From the tool's definition Tool name 'get_agent_status' and description 'Get status information for agents in the system' indicates a query operation that retrieves current state/status data without modification or side effects.
Attacks that exploit this kind of access
Get status information for agents in the system. It is categorised as a Read tool in the Sentient Brain Smithery MCP Server, which means it retrieves data without modifying state.
Register the Sentient Brain Smithery 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 Sentient Brain Smithery. 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 Sentient Brain Smithery MCP server (mbpfws/sentient-brain-smithery). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →