Understand what BaseQL is good at and what it kind of sucks at
AI agents call get_capabilities to retrieve information from BaseQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a purely informational tool that queries and returns metadata about the service's capabilities. It has no side effects, cannot modify state, execute code, or affect blockchain data. The blast radius of misuse is minimal—an agent could only receive potentially misleading information about what the service can do, which is inconsequential.
From the tool's definition Tool name 'get_capabilities' and description indicate it retrieves informational content about BaseQL's strengths and weaknesses. No data modification, execution, deletion, or financial operation is performed.
Attacks that exploit this kind of access
Understand what BaseQL is good at and what it kind of sucks at. It is categorised as a Read tool in the BaseQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BaseQL MCP Server MCP server in PolicyLayer and add a rule for get_capabilities: 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 BaseQL MCP Server. Nothing to install.
get_capabilities 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_capabilities 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_capabilities. 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_capabilities is provided by the BaseQL MCP Server MCP server (jnix2007/baseql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_capabilities is one line of BaseQL MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →