offline_mode_status
AI agents call offline_mode_status to retrieve information from DevDocs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to return status information about offline mode without modifying, executing operations, or deleting data. It is a read-only query that returns state information. Severity is low because even if misused by an agent, retrieving status information has minimal blast radius and no side effects.
From the tool's definition Tool name 'offline_mode_status' indicates a status query operation with no parameters described. The empty description and naming convention suggest it retrieves or queries the current state of offline caching functionality, consistent with other Read…
Attacks that exploit this kind of access
offline_mode_status. It is categorised as a Read tool in the DevDocs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DevDocs MCP Server MCP server in PolicyLayer and add a rule for offline_mode_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 DevDocs MCP Server. Nothing to install.
offline_mode_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 offline_mode_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 offline_mode_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.
offline_mode_status is provided by the DevDocs MCP Server MCP server (javierdevcol/devdocs-mcp). 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 →