aap_create_schedule
AI agents use aap_create_schedule to create or update resources in AAP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AAP MCP Server environment.
The tool name follows the 'aap_create_*' pattern seen in sibling tools (aap_create_credential, aap_create_group, etc.), all of which create new resources. Schedules in AAP trigger automated job runs, so creating one is a Write operation with moderate blast radius (could cause unintended automation runs). Confidence is reduced due to empty description.
From the tool's definition Tool name: aap_create_schedule — 'create' prefix strongly implies creating a new scheduling resource in Ansible Automation Platform.
Attacks that exploit this kind of access
aap_create_schedule. It is categorised as a Write tool in the AAP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AAP MCP Server MCP server in PolicyLayer and add a rule for aap_create_schedule: 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 MCP Server. Nothing to install.
aap_create_schedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the aap_create_schedule 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 aap_create_schedule. 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.
aap_create_schedule is provided by the AAP MCP Server MCP server (srinivassrinu842/aap-mcp-server). 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 →