create_instance_trigger
Create a webhook, cron, or connector-sync trigger on a subscribed private instance. Use sync_connector with config.provider and config.grant_id for Google Drive or Zoho WorkDrive folder syncs. An action the instance
This record as markdown: /tools/io-github-proagentstore-platform/create-instance-trigger.md
What create_instance_trigger does on ProAgentStore
AI agents use create_instance_trigger to create or update resources in ProAgentStore, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ProAgentStore environment.
Why create_instance_trigger is rated Medium
Creates triggers that automate data syncing and webhooks, modifying instance configuration with potential side effects.
From the tool's definition Create a webhook, cron, or connector-sync trigger on a subscribed private instance.
Attacks that exploit this kind of access
The rule that runs create_instance_trigger 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 create_instance_trigger, this is the rule to start with:
create_instance_trigger stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_instance_trigger call is checked against it from then on.
Questions about create_instance_trigger
Create a webhook, cron, or connector-sync trigger on a subscribed private instance. Use sync_connector with config.provider and config.grant_id for Google Drive or Zoho WorkDrive folder syncs. An action the instance. It is categorised as a Write tool in the ProAgentStore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for create_instance_trigger: 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.
create_instance_trigger is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_instance_trigger 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 create_instance_trigger. 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.
create_instance_trigger 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