AI agents call get_agent_status to retrieve information from Agent Collaboration MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the current status of running agents without causing side effects, modifying data, executing code, or triggering external operations. It is a passive monitoring/observational function that fits squarely into the Read category. Severity is low because reading status information has minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_agent_status' and description 'Get status of agents' indicate a query/retrieval operation with no modification or execution of code.
Documented attack patterns abuse exactly the kind of access get_agent_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Collaboration MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_agent_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_agent_status": {}
}
}get_agent_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get status of agents. It is categorised as a Read tool in the Agent Collaboration MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Agent Collaboration MCP Server 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 Agent Collaboration MCP Server. 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 Agent Collaboration MCP Server MCP server (nishimoto265/agent_collaboration_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent Collaboration MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Agent Collaboration MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.