AI agents call remnote_status to retrieve information from Remnote without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about the bridge connection and capabilities. It performs no data modifications, deletions, or external operations. The mention of 'write-policy capabilities' refers to checking what write operations are allowed, not performing them. This is a read-only health-check utility, making it a Read category tool with low severity.
From the tool's definition Tool description states it 'Check[s] bridge connection health, compatibility warnings, and write-policy capabilities' — purely diagnostic and informational with no side effects.
Attacks that exploit this kind of access
Check bridge connection health, compatibility warnings, and write-policy capabilities. Recommended once per session before write operations. It is categorised as a Read tool in the Remnote MCP Server, which means it retrieves data without modifying state.
Register the Remnote MCP server in PolicyLayer and add a rule for remnote_status: 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 Remnote. Nothing to install.
remnote_status 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 remnote_status 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 remnote_status. 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.
remnote_status is provided by the Remnote MCP server (remnote-mcp-server). 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 →