detect_booking_plugin

Detect active booking/events plugin (Amelia, Simply Schedule Appointments, The Events Calendar). Returns plugin name, version, service/event counts.

SERVERElementify MCP SOURCEvamerli/elementify-mcp

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/vamerli-elementify-mcp/detect-booking-plugin.md

WHAT IT DOES

What detect_booking_plugin does on Elementify MCP

AI agents call detect_booking_plugin to retrieve information from Elementify MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why detect_booking_plugin is rated Low

Even though detect_booking_plugin only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs detect_booking_plugin safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Elementify MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For detect_booking_plugin, this is the rule to start with:

detect_booking_plugin Allowed

detect_booking_plugin is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "detect_booking_plugin": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Elementify MCP, apply this rule, and every detect_booking_plugin call is checked against it from then on.

FAQ

Questions about detect_booking_plugin

What does the detect_booking_plugin tool do? +

Detect active booking/events plugin (Amelia, Simply Schedule Appointments, The Events Calendar). Returns plugin name, version, service/event counts. It is categorised as a Read tool in the Elementify MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on detect_booking_plugin? +

Register the Elementify MCP server in PolicyLayer and add a rule for detect_booking_plugin: 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 Elementify MCP. Nothing to install.

What risk level is detect_booking_plugin? +

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

Can I rate-limit detect_booking_plugin? +

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

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

detect_booking_plugin is provided by the Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Elementify, and thousands of servers like it.

This server

All 254 Elementify tools →

Across the catalogue

detect_slop on Slop Cop → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →