q402_redstone_trigger_list

List the RedStone triggers on the user

SERVERQ402 Mcp SOURCE@quackai/q402-mcp

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-bitgett-q402-mcp/q402-redstone-trigger-list.md

WHAT IT DOES

What q402_redstone_trigger_list does on Q402 Mcp

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

RISK

Why q402_redstone_trigger_list is rated Low

The tool lists (reads) RedStone triggers associated with a user. This is a read-only query operation with no modifications, deletions, or financial transactions. Low severity as it only exposes configuration/metadata information.

From the tool's definition "List the RedStone triggers on the user" — purely retrieves/queries existing trigger data with no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs q402_redstone_trigger_list safely

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

q402_redstone_trigger_list Allowed

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

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

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

FAQ

Questions about q402_redstone_trigger_list

What does the q402_redstone_trigger_list tool do? +

List the RedStone triggers on the user. It is categorised as a Read tool in the Q402 Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on q402_redstone_trigger_list? +

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

What risk level is q402_redstone_trigger_list? +

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

Can I rate-limit q402_redstone_trigger_list? +

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

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

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

KEEP EXPLORING

More on Q402, and thousands of servers like it.

This server

All 41 Q402 tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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