New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_role_info

A read tool on the Ludus Fast MCP server.

SERVERLudus FastMCP SOURCEtjnull/ludus-fastmcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tjnull-ludus-fastmcp/get-role-info.md

What get_role_info does on Ludus FastMCP

AI agents call get_role_info 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 get_role_info is rated Low

The naming convention strongly suggests this tool retrieves information about Ansible roles (consistent with sibling tool 'apply_adversary_profile' and server's 'Ansible role management' capability) without modifying state. No destructive, executable, or side-effect keywords are evident. Low severity because reading role metadata poses minimal security risk.

From the tool's definition Tool name 'get_role_info' indicates a retrieval operation. Prefix 'get_' and suffix '_info' both signify query/fetch semantics typical of Read category tools. Description is empty, preventing detailed assessment.

Questions about get_role_info

What does the get_role_info tool do? +

get_role_info 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.

How do I enforce a policy on get_role_info? +

Register the Ludus Fast MCP server in PolicyLayer and add a rule for get_role_info: 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.

What risk level is get_role_info? +

get_role_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_role_info? +

Yes. Add a rate_limit block to the get_role_info 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.

How do I block get_role_info completely? +

Set action: deny in the PolicyLayer policy for get_role_info. 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.

What MCP server provides get_role_info? +

get_role_info 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ludus Fast's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.