check_for_updates

Check if a newer version of cib7-mcp is available on GitHub. If an update is available, ask the user before calling self_update.

Server CIB Seven MCP Server krixerx/cib7-mcp
Category Read
Risk class Low
Parameters 00 required

What check_for_updates does on CIB Seven MCP Server

AI agents call check_for_updates to retrieve information from CIB Seven MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_for_updates needs a policy

This tool merely queries external state (GitHub for version information) and reports findings. It does not execute updates, modify data, or change system state. The actual update action (self_update) is decoupled and requires user consent. Classification as Read is appropriate.

From the tool's definition Tool checks for availability of updates on GitHub—a query/retrieval operation with no side effects. Description explicitly states it 'asks the user before calling self_update', confirming the check itself is non-destructive.

Questions about check_for_updates

What does the check_for_updates tool do? +

Check if a newer version of cib7-mcp is available on GitHub. If an update is available, ask the user before calling self_update. It is categorised as a Read tool in the CIB Seven MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_for_updates? +

Register the CIB Seven MCP Server MCP server in PolicyLayer and add a rule for check_for_updates: 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 CIB Seven MCP Server. Nothing to install.

What risk level is check_for_updates? +

check_for_updates is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_for_updates? +

Yes. Add a rate_limit block to the check_for_updates 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.

How do I block check_for_updates completely? +

Set action: deny in the PolicyLayer policy for check_for_updates. 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.

What MCP server provides check_for_updates? +

check_for_updates is provided by the CIB Seven MCP Server MCP server (krixerx/cib7-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.