check_updates
Explicitly check featureboard.ai for a newer FeatureBoard release. This makes exactly ONE outbound HTTPS
This record as markdown: /tools/ai-featureboard-featureboard/check-updates.md
What check_updates does on FeatureBoard
AI agents call check_updates to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_updates is rated Low
The tool performs a single outbound HTTPS request to check for updates. This is purely informational retrieval—it queries remote state (availability of a newer release) without modifying any local or remote data. No code is executed, no data is written or deleted, and no external operations are triggered beyond the GET-like request itself.
From the tool's definition Tool explicitly 'check[s] featureboard.ai for a newer FeatureBoard release' and 'makes exactly ONE outbound HTTPS' request. This is a read-only query to a remote server that retrieves version information with no modifications, deletions, or side effects.
Attacks that exploit this kind of access
The rule that runs check_updates safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_updates, this is the rule to start with:
check_updates 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 FeatureBoard, apply this rule, and every check_updates call is checked against it from then on.
Questions about check_updates
Explicitly check featureboard.ai for a newer FeatureBoard release. This makes exactly ONE outbound HTTPS. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for check_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 FeatureBoard. Nothing to install.
check_updates 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_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.
Set action: deny in the PolicyLayer policy for check_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.
check_updates is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue