Get Dolibarr system status
AI agents call get_status to retrieve information from Dolibarr MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the status of the Dolibarr system (likely uptime, database health, or operational state). It performs no data modification, creates no side effects, and executes no arbitrary code—it is purely informational. This is a straightforward Read operation with minimal security impact even if misused by an AI agent.
From the tool's definition Tool name 'get_status' and description 'Get Dolibarr system status' indicate a retrieval operation that queries system information without modifying data.
Attacks that exploit this kind of access
Get Dolibarr system status. It is categorised as a Read tool in the Dolibarr MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dolibarr MCP Server MCP server in PolicyLayer and add a rule for get_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 Dolibarr MCP Server. Nothing to install.
get_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 get_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 get_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.
get_status is provided by the Dolibarr MCP Server MCP server (marioser/dolibarr-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 →