Read the cross-agent activity feed plus a snapshot of every agent
AI agents call get_activity to retrieve information from Mcp Switchboard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about agent activity and status without any side effects. It queries existing data (activity feed and agent snapshots) without creating, modifying, deleting, or executing anything. This is a straightforward read operation with minimal risk if misused—the worst outcome is information disclosure about agent coordination state.
From the tool's definition Tool name 'get_activity' with description 'Read the cross-agent activity feed plus a snapshot of every agent' explicitly indicates data retrieval with no modification or execution capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Read the cross-agent activity feed plus a snapshot of every agent. It is categorised as a Read tool in the Mcp Switchboard MCP Server, which means it retrieves data without modifying state.
Register the Mcp Switchboard MCP server in PolicyLayer and add a rule for get_activity: 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 Mcp Switchboard. Nothing to install.
get_activity 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_activity 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_activity. 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_activity is provided by the Mcp Switchboard MCP server (jemplayer82/mcp-switchboard). 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 →