Get SolSentry system-wide threat intelligence statistics:
AI agents call get_network_stats to retrieve information from SolSentry MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system-wide threat intelligence statistics about the Solana network and SolSentry's detection metrics. It does not create, modify, delete, execute code, or commit financial transactions. The 'get' verb and informational nature (returning statistics for threat detection awareness) classify it as a Read operation with low severity and high confidence.
From the tool's definition Tool description explicitly states 'Get' statistics—a retrieval operation with no modification, deletion, or execution of external code. The purpose is to 'check' and 'detect' threats via querying threat intelligence data, consistent with read-only operations.
Attacks that exploit this kind of access
Get SolSentry system-wide threat intelligence statistics:. It is categorised as a Read tool in the SolSentry MCP MCP Server, which means it retrieves data without modifying state.
Register the SolSentry MCP server in PolicyLayer and add a rule for get_network_stats: 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 SolSentry MCP. Nothing to install.
get_network_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_network_stats 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 get_network_stats. 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.
get_network_stats is provided by the SolSentry MCP server (solsentry/solsentry-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →