Run a job template by ID, optionally with extra_vars.
AI agents invoke run_job to trigger actions in AAP Enterprise MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool invokes job execution in Red Hat's Automation Platform, a deployment and infrastructure orchestration system. Job templates can perform arbitrary actions (provision resources, configure systems, deploy applications, run scripts) depending on their configuration and extra_vars. The effects are contingent on what the job template does and what variables are passed, making this Execute rather than Write.
From the tool's definition 'Run a job template by ID' — this tool executes an Ansible automation job with configurable parameters (extra_vars), which triggers external operations whose effects depend on arguments (playbook execution, infrastructure changes, etc.).
Documented attack patterns abuse exactly the kind of access run_job gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AAP Enterprise MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_job:
{
"version": "1",
"default": "deny",
"tools": {
"run_job": {
"limits": [
{
"counter": "run_job_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_job stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run a job template by ID, optionally with extra_vars. It is categorised as a Execute tool in the AAP Enterprise MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AAP Enterprise MCP Server MCP server in PolicyLayer and add a rule for run_job: 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 AAP Enterprise MCP Server. Nothing to install.
run_job is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_job 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 run_job. 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.
run_job is provided by the AAP Enterprise MCP Server MCP server (sibilleb/aap-enterprise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 69 AAP Enterprise MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
69 AAP Enterprise MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.