Get the ansible tags available for use with deploy. This shows all available deployment tags that can be used with the deploy_range tool. Requires admin privileges to get tags for other users.
AI agents call get_tags to retrieve information from LudusMCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays available ansible tags for deployment configuration. It does not create, modify, delete, execute, or move resources. The only permission model mentioned is that it 'requires admin privileges to get tags for other users,' which is an access control consideration but does not change the fundamental read-only nature of the operation.
From the tool's definition Tool name is 'get_tags' and description states it 'shows all available deployment tags' — a pure query/retrieval operation with 'no side effects'. The word 'Get' and 'shows' indicate read-only access to configuration metadata.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access get_tags gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LudusMCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_tags:
{
"version": "1",
"default": "deny",
"tools": {
"get_tags": {}
}
}get_tags 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 the ansible tags available for use with deploy. This shows all available deployment tags that can be used with the deploy_range tool. Requires admin privileges to get tags for other users. It is categorised as a Read tool in the LudusMCP Server MCP Server, which means it retrieves data without modifying state.
Register the LudusMCP Server MCP server in PolicyLayer and add a rule for get_tags: 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 LudusMCP Server. Nothing to install.
get_tags 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_tags 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_tags. 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_tags is provided by the LudusMCP Server MCP server (noctedefensor/ludusmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 LudusMCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 LudusMCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.