sol_validators
Solana validator set from getVoteAccounts: active and delinquent counts, total active stake, Nakamoto coefficient (fewest validators controlling > 33.3% of stake), the top validators by stake with commission, stake %, last vote, root slot and last-epoch vote credits, or one validator by vote or i...
This record as markdown: /tools/com-it-scorptech-x402/sol-validators.md
What sol_validators does on ScorpTech x402 API
AI agents use sol_validators to create or update resources in ScorpTech x402 API, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScorpTech x402 API environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Top validators by stake to list |
validator | string | — | Look up one validator by vote account or identity (node) pubkey |
Parameters from the server's own tool schema.
Why sol_validators is rated Medium
An AI agent can call sol_validators faster than any human can review: one bad instruction and it creates or modifies resources in ScorpTech x402 API by the hundred, each call as confident as the last.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs sol_validators 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 sol_validators, this is the rule to start with:
sol_validators stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every sol_validators call is checked against it from then on.
Questions about sol_validators
Solana validator set from getVoteAccounts: active and delinquent counts, total active stake, Nakamoto coefficient (fewest validators controlling > 33.3% of stake), the top validators by stake with commission, stake %, last vote, root slot and last-epoch vote credits, or one validator by vote or identity key. Cached 5 minutes. Public Solana RPC, read-only. Price: $0.005 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/sol-validators. It is categorised as a Write tool in the ScorpTech x402 API MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
sol_validators accepts 2 parameters: limit, validator. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for sol_validators: 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.
sol_validators is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sol_validators 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.
Set action: deny in the PolicyLayer policy for sol_validators. 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.
sol_validators 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.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue