lynch_bell

SERVERScorpTech x402 API SOURCEhttps://scorptech.it.com/api/x402/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-it-scorptech-x402/lynch-bell.md

WHAT IT DOES

What lynch_bell does on ScorpTech x402 API

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

Parameter	Type	Required	Description
`n`	integer	Yes

Parameters from the server's own tool schema.

RISK

Why lynch_bell is rated Low

Even though lynch_bell only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lynch_bell safely

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

lynch_bell Allowed

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

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

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

FAQ

Questions about lynch_bell

What does the lynch_bell tool do? +

Whether every digit of n is nonzero, the digits are all different, and each digit divides n. 12, 15, 24, 124, and 135 do. 10, 11, and 13 do not. n runs from 1 to 1000000000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/lynch-bell. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.

What parameters does lynch_bell accept? +

lynch_bell accepts 1 parameter: n. Required: n. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on lynch_bell? +

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

What risk level is lynch_bell? +

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

Can I rate-limit lynch_bell? +

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

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

lynch_bell is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScorpTech x402 API, and thousands of servers like it.

This server

All 1012 ScorpTech x402 API tools →

Across the catalogue

The MCP Attack Database →

Guides

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