Get information about the system configuration and acceleration status
AI agents call get_system_info to retrieve information from MCP Docling Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system configuration and acceleration status information. It is purely informational with no side effects, making it a Read category tool. The severity is low because system configuration information is typically non-sensitive in isolation and does not enable further attacks or data compromise directly. The confidence is high because the description unambiguously describes a retrieval operation.
From the tool's definition Tool description states 'Get information about the system configuration and acceleration status' — a query operation that retrieves system metadata with no data modification, deletion, or code execution capability.
Documented attack patterns abuse exactly the kind of access get_system_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Docling Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_system_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_system_info": {}
}
}get_system_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get information about the system configuration and acceleration status. It is categorised as a Read tool in the MCP Docling Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Docling Server MCP server in PolicyLayer and add a rule for get_system_info: 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 MCP Docling Server. Nothing to install.
get_system_info 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_system_info 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_system_info. 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_system_info is provided by the MCP Docling Server MCP server (zanetworker/mcp-docling). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Docling Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MCP Docling Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.