run_query_preset · Tick MCP: Risk & Policy

WHAT IT DOES

What run_query_preset does on Tick

AI agents invoke run_query_preset to trigger actions in Tick. 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 run_query_preset needs a policy

While 'query' might suggest a Read operation, the explicit 'Execute' verb and the context of a task management system (where presets could contain update/delete operations) places this in Execute rather than Read. The tool's actual behavior depends on the preset's contents, which an AI agent cannot fully predict.

From the tool's definition Tool name is 'run_query_preset' with description 'Execute a saved query preset.' The verb 'Execute' directly indicates code/query execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_query_preset Rate-limited

run_query_preset 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": {
    "run_query_preset": {
      "limits": [
        {
          "counter": "run_query_preset_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 Tick, so you can run agents against it safely.

FAQ

Questions about run_query_preset

What does the run_query_preset tool do? +

Execute a saved query preset. It is categorised as a Execute tool in the Tick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_query_preset? +

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

What risk level is run_query_preset? +

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

Can I rate-limit run_query_preset? +

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

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

run_query_preset is provided by the Tick MCP server (kpihx/tick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.