move_ansible_role_scope
A write tool on the Ludus Fast MCP server.
This record as markdown: /tools/tjnull-ludus-fastmcp/move-ansible-role-scope.md
What move_ansible_role_scope does on Ludus FastMCP
AI agents use move_ansible_role_scope to create or update resources in Ludus FastMCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ludus FastMCP environment.
Why move_ansible_role_scope is rated Medium
Likely modifies Ansible role scope assignments within cyber range, reversible but impactful to testing infrastructure.
From the tool's definition uninformative description; 'move' suggests modification; Ansible role scope management context
Attacks that exploit this kind of access
The rule that runs move_ansible_role_scope safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ludus FastMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_ansible_role_scope, this is the rule to start with:
move_ansible_role_scope stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ludus FastMCP, apply this rule, and every move_ansible_role_scope call is checked against it from then on.
Questions about move_ansible_role_scope
move_ansible_role_scope is a write tool on the Ludus Fast MCP server. It is categorised as a Write tool in the Ludus FastMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for move_ansible_role_scope: 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 Ludus FastMCP. Nothing to install.
move_ansible_role_scope 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 move_ansible_role_scope 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 move_ansible_role_scope. 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.
move_ansible_role_scope is provided by the Ludus Fast MCP server (tjnull/ludus-fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ludus Fast, and thousands of servers like it.
This server
Across the catalogue