Get variables for an Ansible role (Ludus 2.0 only). Args: role_name: Name of the role Returns: Role variables
AI agents call get_ansible_role_vars to retrieve information from Ludus FastMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves Ansible role variables without modifying any configuration or executing actions. It is a straightforward query operation with no side effects. Severity is low because leaked variables might contain sensitive data, but the tool itself performs no destructive, financial, or executable operations—it only reads existing state.
From the tool's definition Tool name 'get_ansible_role_vars' and description 'Get variables for an Ansible role' with return type 'Role variables'. The verb 'get' and lack of modification language indicate data retrieval only.
Documented attack patterns abuse exactly the kind of access get_ansible_role_vars gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ludus FastMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_ansible_role_vars:
{
"version": "1",
"default": "deny",
"tools": {
"get_ansible_role_vars": {}
}
}get_ansible_role_vars is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get variables for an Ansible role (Ludus 2.0 only). Args: role_name: Name of the role Returns: Role variables. It is categorised as a Read tool in the Ludus FastMCP MCP Server, which means it retrieves data without modifying state.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for get_ansible_role_vars: 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.
get_ansible_role_vars 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 get_ansible_role_vars 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 get_ansible_role_vars. 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.
get_ansible_role_vars 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.
Deterministic rules across all 201 Ludus FastMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
201 Ludus FastMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.