igniteonly_policy

Return the PinballWake IgniteOnlyAPI guardrails. This is the green ignite sibling to NudgeOnly: verified worker wake packets only, no build, merge, approval, closure, or truth-setting.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/igniteonly-policy.md

WHAT IT DOES

What igniteonly_policy does on UnClick

AI agents call igniteonly_policy to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why igniteonly_policy is rated Low

The tool appears to fetch and return policy or configuration guardrails for the IgniteOnlyAPI. This is a read/query operation with no apparent side effects. The description explicitly states it returns guardrails and excludes build, merge, approval, closure, or truth-setting actions. Confidence is moderate because the description is somewhat opaque and domain-specific, making the full scope unclear.

From the tool's definition 'Return the PinballWake IgniteOnlyAPI guardrails' — the tool returns/retrieves policy/guardrail information

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs igniteonly_policy safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For igniteonly_policy, this is the rule to start with:

igniteonly_policy Allowed

igniteonly_policy 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": {
    "igniteonly_policy": {}
  }
}

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

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

FAQ

Questions about igniteonly_policy

What does the igniteonly_policy tool do? +

Return the PinballWake IgniteOnlyAPI guardrails. This is the green ignite sibling to NudgeOnly: verified worker wake packets only, no build, merge, approval, closure, or truth-setting. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on igniteonly_policy? +

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

What risk level is igniteonly_policy? +

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

Can I rate-limit igniteonly_policy? +

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

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

igniteonly_policy is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

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