Get server version and check for updates from GitHub. Returns the current installed version, latest available version, whether an update is available, and the command to update. If update_available is true, inform the user that a new version is available and suggest updating.
AI agents call check_version to retrieve information from Fusebase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves version metadata and update status information without making any changes to the system, modifying data, or executing code. It is a read-only query operation that returns static information about version numbers and availability. The returned 'command to update' is just informational text, not an execution of that command.
From the tool's definition Tool name 'check_version' and description 'Get server version and check for updates from GitHub. Returns the current installed version, latest available version, whether an update is available, and the command to update.' indicate pure information retrieval…
Attacks that exploit this kind of access
Get server version and check for updates from GitHub. Returns the current installed version, latest available version, whether an update is available, and the command to update. If update_available is true, inform the user that a new version is available and suggest updating. It is categorised as a Read tool in the Fusebase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fusebase MCP Server MCP server in PolicyLayer and add a rule for check_version: 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 Fusebase MCP Server. Nothing to install.
check_version 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_version 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_version. 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_version is provided by the Fusebase MCP Server MCP server (ryan-haver/fusebase-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 →