AI agents call get_team_status to retrieve information from ATMcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays monitoring/status information about a distributed team system. It is purely informational—it queries existing state (agent availability, task metrics, progress indicators, knowledge inventory) without creating, modifying, deleting, or executing any operations. No financial, destructive, or code-execution impact is possible.
From the tool's definition Tool name 'get_team_status' and description 'One-shot snapshot: agents online, task counts, goal progress %, knowledge count, head cursor' indicate a read-only query of system state with no modifications, side effects, or external operations triggered.
Attacks that exploit this kind of access
One-shot snapshot: agents online, task counts, goal progress %, knowledge count, head cursor. It is categorised as a Read tool in the ATMcp MCP Server, which means it retrieves data without modifying state.
Register the AT MCP server in PolicyLayer and add a rule for get_team_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 ATMcp. Nothing to install.
get_team_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_team_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_team_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_team_status is provided by the AT MCP server (midcheck/atmcp). 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 →