capture_agent_events

Capture recent events/output from a descendant child agent task. Returns a compact, summarized event list.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/capture-agent-events.md

What capture_agent_events does on CoWork OS

AI agents call capture_agent_events to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why capture_agent_events is rated Low

This tool retrieves historical event data from child agent tasks and returns a summarized view. It is a read-only operation with no side effects—it queries existing state without altering it. The low severity reflects minimal risk from misuse: an agent accessing events from its own task hierarchy poses negligible harm.

From the tool's definition Tool description states it 'Capture[s] recent events/output from a descendant child agent task. Returns a compact, summarized event list.' The verb 'capture' in this context means retrieve/query, and 'returns' confirms data retrieval with no modification.

Questions about capture_agent_events

What does the capture_agent_events tool do? +

Capture recent events/output from a descendant child agent task. Returns a compact, summarized event list. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on capture_agent_events? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for capture_agent_events: 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 CoWork OS. Nothing to install.

What risk level is capture_agent_events? +

capture_agent_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit capture_agent_events? +

Yes. Add a rate_limit block to the capture_agent_events 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.

How do I block capture_agent_events completely? +

Set action: deny in the PolicyLayer policy for capture_agent_events. 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.

What MCP server provides capture_agent_events? +

capture_agent_events is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on CoWork OS, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of CoWork OS's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.