List every rule in the currently loaded JamJet policy, in declaration order. Each entry includes the rule index, action (allow / block / require_approval / audit), and the glob pattern it matches. Use this to inspect the active policy without reading the YAML file directly, or to verify a rollout...
AI agents call policy_list_rules to retrieve information from Jamjet Policy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves policy rules for inspection purposes only. It has no side effects, does not modify any data, and does not execute or trigger external operations. It is a straightforward query/list operation that falls clearly into the Read category. The "Read-only" designation in the description confirms this classification.
From the tool's definition The tool description states it is "Read-only" and its purpose is to "List every rule in the currently loaded JamJet policy" and "inspect the active policy". It retrieves and queries policy configuration data without modifying, executing, or deleting anything.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every rule in the currently loaded JamJet policy, in declaration order. Each entry includes the rule index, action (allow / block / require_approval / audit), and the glob pattern it matches. Use this to inspect the active policy without reading the YAML file directly, or to verify a rollout placed rules in the expected order. Read-only. It is categorised as a Read tool in the Jamjet Policy MCP Server, which means it retrieves data without modifying state.
Register the Jamjet Policy MCP server in PolicyLayer and add a rule for policy_list_rules: 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 Jamjet Policy. Nothing to install.
policy_list_rules 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 policy_list_rules 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 policy_list_rules. 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.
policy_list_rules is provided by the Jamjet Policy MCP server (jamjet-labs/jamjet-policy). 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 →