check_update

Check if a newer version is available on GitHub.

Server Nexus Memory neboy72/nexus-memory
Category Read
Risk class Low
Parameters 00 required

What check_update does on Nexus Memory

AI agents call check_update to retrieve information from Nexus Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_update needs a policy

This tool performs a read-only check against GitHub to determine version availability. It retrieves data (version status) with no side effects, modifications to the memory system, or execution of code. The operation is informational only and poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'check_update' and description 'Check if a newer version is available on GitHub' indicate a query operation that retrieves version information without modifying any local state or triggering installations.

Questions about check_update

What does the check_update tool do? +

Check if a newer version is available on GitHub. It is categorised as a Read tool in the Nexus Memory MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_update? +

Register the Nexus Memory MCP server in PolicyLayer and add a rule for check_update: 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 Nexus Memory. Nothing to install.

What risk level is check_update? +

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

Can I rate-limit check_update? +

Yes. Add a rate_limit block to the check_update 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_update completely? +

Set action: deny in the PolicyLayer policy for check_update. 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_update? +

check_update is provided by the Nexus Memory MCP server (neboy72/nexus-memory). 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.