Low Risk

request_demo

Submits an open demo request without picking a specific time. Use this when the user does not want to choose a slot — the Modulos team will reach out within 1 business day.

Part of the Modulos Demo Booking server.

request_demo is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MODULOS DEMO BOOKING →

Free to start. No card required.

AI agents call request_demo 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 request_demo 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "request_demo": {}
  }
}

See the full Modulos Demo Booking policy for all 4 tools.

Get this rule live on your own Modulos Demo Booking server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MODULOS DEMO BOOKING →

These attack patterns abuse exactly the kind of access request_demo gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so request_demo only ever does what you allow.

SECURE MODULOS DEMO BOOKING →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the request_demo tool do? +

Submits an open demo request without picking a specific time. Use this when the user does not want to choose a slot — the Modulos team will reach out within 1 business day.. It is categorised as a Read tool in the Modulos Demo Booking MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on request_demo? +

Register the Modulos Demo Booking MCP server in PolicyLayer and add a rule for request_demo: 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.

What risk level is request_demo? +

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

Can I rate-limit request_demo? +

Yes. Add a rate_limit block to the request_demo 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 request_demo completely? +

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

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

Enforce policy on every Modulos Demo Booking tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.