list_instance_trigger_events

Read recent event history for one configured instance trigger, including received/running/succeeded/failed entries.

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/list-instance-trigger-events.md

WHAT IT DOES

What list_instance_trigger_events does on ProAgentStore

AI agents call list_instance_trigger_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.

RISK

Why list_instance_trigger_events is rated Low

Tool retrieves and queries event history with no modification or side effects.

From the tool's definition Read recent event history for one configured instance trigger

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_instance_trigger_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 list_instance_trigger_events, this is the rule to start with:

list_instance_trigger_events Allowed

list_instance_trigger_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_instance_trigger_events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every list_instance_trigger_events call is checked against it from then on.

FAQ

Questions about list_instance_trigger_events

What does the list_instance_trigger_events tool do? +

Read recent event history for one configured instance trigger, including received/running/succeeded/failed entries. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_instance_trigger_events? +

Register the ProAgentStore MCP server in PolicyLayer and add a rule for list_instance_trigger_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.

What risk level is list_instance_trigger_events? +

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

Can I rate-limit list_instance_trigger_events? +

Yes. Add a rate_limit block to the list_instance_trigger_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 list_instance_trigger_events completely? +

Set action: deny in the PolicyLayer policy for list_instance_trigger_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 list_instance_trigger_events? +

list_instance_trigger_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.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →