AI agents call get_restricted_software 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 or queries existing restricted software configuration data from Jamf Pro without any side effects, state changes, or execution of commands. It is a straightforward inventory/query operation consistent with other sibling tools like 'get_buildings' and 'get_computer_inventory'.
From the tool's definition Tool name is 'get_restricted_software' and description states 'Get list of all restricted software.' The verb 'Get' and action 'list' indicate data retrieval with no modification or execution.
Attacks that exploit this kind of access
Get list of all restricted software. 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_restricted_software: 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_restricted_software 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_restricted_software 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_restricted_software. 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_restricted_software 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 →