Low Risk

rundeck_list_acl_policies

List all system-level ACL policy files

Risk signalsAdmin/system-level operation

Part of the Rundeck server.

rundeck_list_acl_policies is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE RUNDECK →

Free to start. No card required.

AI agents call rundeck_list_acl_policies to retrieve information from Rundeck without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though rundeck_list_acl_policies only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "rundeck_list_acl_policies": {}
  }
}

See the full Rundeck policy for all 50 tools.

Get this rule live on your own Rundeck server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY RUNDECK →

View all 50 tools →

These attack patterns abuse exactly the kind of access rundeck_list_acl_policies gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so rundeck_list_acl_policies only ever does what you allow.

SECURE RUNDECK →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the rundeck_list_acl_policies tool do? +

List all system-level ACL policy files. It is categorised as a Read tool in the Rundeck MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on rundeck_list_acl_policies? +

Register the Rundeck MCP server in PolicyLayer and add a rule for rundeck_list_acl_policies: 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 Rundeck. Nothing to install.

What risk level is rundeck_list_acl_policies? +

rundeck_list_acl_policies is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit rundeck_list_acl_policies? +

Yes. Add a rate_limit block to the rundeck_list_acl_policies 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.

How do I block rundeck_list_acl_policies completely? +

Set action: deny in the PolicyLayer policy for rundeck_list_acl_policies. 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.

What MCP server provides rundeck_list_acl_policies? +

rundeck_list_acl_policies is provided by the Rundeck MCP server (rundeck-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Rundeck tool call.

Deterministic rules across all 50 Rundeck tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.