visible_points

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/visible-points.md

WHAT IT DOES

What visible_points does on ScorpTech x402 API

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

Even though visible_points 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

visible_points Allowed

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

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

FAQ

Questions about visible_points

What does the visible_points tool do? +

How many lattice points (x, y) with 1 <= x,y <= n are visible from the origin, meaning gcd(x, y) = 1. The 1-square has 1, the 2-square has 3, and the 5-square has 19. n runs from 1 to 100000. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/visible-points. 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 visible_points accept? +

visible_points 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 visible_points? +

Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for visible_points: 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 visible_points? +

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

Can I rate-limit visible_points? +

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

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

visible_points 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 →