AI agents call get_service_status to retrieve information from Sysprobe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only retrieves and queries systemd unit status and journal logs. It performs no modifications, writes, deletions, command execution, or financial operations. The blast radius of misuse is minimal, as reading service status and logs cannot damage systems or leak sensitive data beyond logs that a user with systemd access can already query.
From the tool's definition Tool retrieves 'Status of a systemd unit + last few journal lines' — both read-only diagnostic operations that query existing state without modification.
Attacks that exploit this kind of access
Status of a systemd unit + last few journal lines. It is categorised as a Read tool in the Sysprobe MCP Server, which means it retrieves data without modifying state.
Register the Sysprobe MCP server in PolicyLayer and add a rule for get_service_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 Sysprobe. Nothing to install.
get_service_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_service_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_service_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_service_status is provided by the Sysprobe MCP server (raindancer118/sysprobe-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 →