update_check
Check for available system updates. Returns information about pending updates and the current train.
This record as markdown: /tools/nasbridge/update-check.md
What update_check does on Nasbridge
AI agents call update_check to retrieve information from Nasbridge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why update_check is rated Low
This tool only retrieves and returns information about available updates without applying any changes. It is a read-only query operation with no side effects.
From the tool's definition Check for available system updates. Returns information about pending updates and the current train.
Attacks that exploit this kind of access
The rule that runs update_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_check, this is the rule to start with:
update_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every update_check call is checked against it from then on.
Questions about update_check
Check for available system updates. Returns information about pending updates and the current train. It is categorised as a Read tool in the Nasbridge MCP Server, which means it retrieves data without modifying state.
Register the Nasbridge MCP server in PolicyLayer and add a rule for update_check: 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 Nasbridge. Nothing to install.
update_check 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 update_check 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 update_check. 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.
update_check is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue