q402_bridge_history

READ-ONLY GUIDANCE TOOL - bridge history via MCP is not yet wired in this release. It

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-bridge-history.md

WHAT IT DOES

What q402_bridge_history does on Q402 Mcp

AI agents call q402_bridge_history 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_bridge_history is rated Low

This is a read-only operation that queries bridge transaction history. It retrieves data without modifying, deleting, or executing any financial transactions. The explicit 'READ-ONLY' label and incomplete implementation ('not yet wired') further confirm it poses minimal risk—it cannot initiate payments, transfers, or destructive actions.

From the tool's definition Tool name q402_bridge_history and description explicitly state 'READ-ONLY GUIDANCE TOOL' and 'bridge history via MCP is not yet wired in this release.' The tool only retrieves historical data with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs q402_bridge_history 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_bridge_history, this is the rule to start with:

q402_bridge_history Allowed

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

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_bridge_history call is checked against it from then on.

FAQ

Questions about q402_bridge_history

What does the q402_bridge_history tool do? +

READ-ONLY GUIDANCE TOOL - bridge history via MCP is not yet wired in this release. It. 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_bridge_history? +

Register the Q402 MCP server in PolicyLayer and add a rule for q402_bridge_history: 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_bridge_history? +

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

Can I rate-limit q402_bridge_history? +

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

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

q402_bridge_history 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

The MCP Attack Database →

Guides

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