AI agents call get_compliance_status to retrieve information from JamfMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves compliance status information about a computer from Jamf Pro. It has no side effects, does not modify data, and does not execute actions. However, severity is rated 'medium' rather than 'low' because compliance status information could be sensitive (revealing security posture, policy violations, or device health state) and could be misused by an AI agent to identify vulnerable systems or…
From the tool's definition Tool name 'get_compliance_status' and description 'Get compliance status for a computer' indicate a retrieval operation with no modification or execution of commands. The verb 'get' and context of querying compliance data align with read-only operations.
Attacks that exploit this kind of access
Get compliance status for a computer. It is categorised as a Read tool in the JamfMCP MCP Server, which means it retrieves data without modifying state.
Register the Jamf MCP server in PolicyLayer and add a rule for get_compliance_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 JamfMCP. Nothing to install.
get_compliance_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_compliance_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_compliance_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_compliance_status is provided by the Jamf MCP server (liquidz00/jamfmcp). 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 →