instance_task_events
Read recent events from a private instance
This record as markdown: /tools/io-github-proagentstore-platform/instance-task-events.md
What instance_task_events does on ProAgentStore
AI agents call instance_task_events to retrieve information from ProAgentStore without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why instance_task_events is rated Low
This tool retrieves historical event data without modifying, deleting, or executing operations. It is a straightforward read operation querying existing event logs from a private instance. The low severity reflects minimal blast radius if misused - an agent could only access event history, which represents information disclosure rather than operational damage.
From the tool's definition Tool description states 'Read recent events from a private instance' - the verb 'Read' and the retrieval-only nature (querying historical events) indicate no modifications, deletions, or side effects.
Attacks that exploit this kind of access
The rule that runs instance_task_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For instance_task_events, this is the rule to start with:
instance_task_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every instance_task_events call is checked against it from then on.
Questions about instance_task_events
Read recent events from a private instance. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for instance_task_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 ProAgentStore. Nothing to install.
instance_task_events 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 instance_task_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.
Set action: deny in the PolicyLayer policy for instance_task_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.
instance_task_events is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
This server
Across the catalogue