Returns a short description of Modulos and the URL where a user can book a demo. Use this first if the user asks what Modulos is or how to talk to the team.
Part of the Modulos Demo Booking server.
Free to start. No card required.
AI agents call get_modulos_info to retrieve information from Modulos Demo Booking without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_modulos_info only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_modulos_info": {}
}
}See the full Modulos Demo Booking policy for all 4 tools.
These attack patterns abuse exactly the kind of access get_modulos_info gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Returns a short description of Modulos and the URL where a user can book a demo. Use this first if the user asks what Modulos is or how to talk to the team.. It is categorised as a Read tool in the Modulos Demo Booking MCP Server, which means it retrieves data without modifying state.
Register the Modulos Demo Booking MCP server in PolicyLayer and add a rule for get_modulos_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 Modulos Demo Booking. Nothing to install.
get_modulos_info 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_modulos_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.
Set action: deny in the PolicyLayer policy for get_modulos_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.
get_modulos_info is provided by the Modulos Demo Booking MCP server (https://www.modulos.ai/api/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Modulos Demo Booking tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.