check_role_installed
A read tool on the Ludus Fast MCP server.
This record as markdown: /tools/tjnull-ludus-fastmcp/check-role-installed.md
What check_role_installed does on Ludus FastMCP
AI agents call check_role_installed to retrieve information from Ludus FastMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_role_installed is rated Low
Based on the naming convention, this tool appears to verify whether an Ansible role is installed in the Ludus environment. This is a read-only query operation with no side effects—it retrieves information about the current state of role installations without creating, modifying, executing, or deleting anything.
From the tool's definition Tool name 'check_role_installed' indicates a status check or verification operation. The verb 'check' typically implies querying or inspecting state without modification. No description provided, which limits certainty.
Attacks that exploit this kind of access
The rule that runs check_role_installed 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 check_role_installed, this is the rule to start with:
check_role_installed is read-only, so it stays allowed. 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 check_role_installed call is checked against it from then on.
Questions about check_role_installed
check_role_installed is a read tool on the Ludus Fast MCP server. 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 check_role_installed: 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.
check_role_installed 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 check_role_installed 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 check_role_installed. 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.
check_role_installed 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