trigger_survey · Inkwell MCP Server MCP: Risk & Policy

WHAT IT DOES

What trigger_survey does on Inkwell MCP Server

AI agents invoke trigger_survey to trigger actions in Inkwell MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why trigger_survey needs a policy

Triggering a survey executes a workflow that initiates data collection and user engagement operations. While not destructive or financial, it performs an action whose outcome depends on supplied arguments, fitting the Execute category.

From the tool's definition 'Trigger a survey' indicates an active operation that initiates a survey workflow. The tool effects depend on the 'specific path or context' argument provided—different contexts would trigger different survey behaviors.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trigger_survey Rate-limited

trigger_survey stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "trigger_survey": {
      "limits": [
        {
          "counter": "trigger_survey_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Inkwell MCP Server, so you can run agents against it safely.

FAQ

Questions about trigger_survey

What does the trigger_survey tool do? +

Trigger a survey for a specific path or context. Returns the survey definition for the client to display. It is categorised as a Execute tool in the Inkwell MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on trigger_survey? +

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

What risk level is trigger_survey? +

trigger_survey is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit trigger_survey? +

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

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

trigger_survey is provided by the Inkwell MCP Server MCP server (mumega-com/inkwell). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

trigger_survey is one line of Inkwell MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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