Get BTCPay Server version and system information.
AI agents call get_server_info to retrieve information from BTCPay Server MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns server metadata (version, system info). It has no side effects, cannot modify state, and poses minimal risk if misused by an AI agent. It belongs in the Read category with low severity.
From the tool's definition Tool name is 'get_server_info' and description states it retrieves 'BTCPay Server version and system information' — purely informational with no modifications, deletions, executions, or financial operations.
Attacks that exploit this kind of access
Get BTCPay Server version and system information. It is categorised as a Read tool in the BTCPay Server MCP MCP Server, which means it retrieves data without modifying state.
Register the BTCPay Server MCP server in PolicyLayer and add a rule for get_server_info: 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 BTCPay Server MCP. Nothing to install.
get_server_info 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_server_info 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_server_info. 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_server_info is provided by the BTCPay Server MCP server (ThomsenDrake/btcpay-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 →