check_access
AI agents call check_access to retrieve information from MCP Solana Internet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the server handles financial operations (Solana payments), this specific tool appears to be a read-only access checker—verifying whether a user has paid/has permission, not executing payments or making state changes. The empty description reduces confidence, but the name and server architecture suggest a simple read operation.
From the tool's definition Tool name 'check_access' suggests querying access status or permissions. Server context involves payment/blockchain integration, but no description provided.
Attacks that exploit this kind of access
check_access. It is categorised as a Read tool in the MCP Solana Internet MCP Server, which means it retrieves data without modifying state.
Register the MCP Solana Internet MCP server in PolicyLayer and add a rule for check_access: 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 MCP Solana Internet. Nothing to install.
check_access 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 check_access 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 check_access. 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.
check_access is provided by the MCP Solana Internet MCP server (waifuai/mcp-solana-internet). 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 →