ml_detect_plugin

Erkennt welches Multilingual-Plugin installiert ist

SERVERWordPress MCP Server SOURCEc-sakel/wp-mcp-server

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/c-sakel-wp-mcp-server/ml-detect-plugin.md

WHAT IT DOES

What ml_detect_plugin does on WordPress MCP Server

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

RISK

Why ml_detect_plugin is rated Low

The tool merely detects and reports which multilingual plugin is active in the WordPress installation. It queries the system state without creating, modifying, executing, or deleting any data or functionality. This is a pure information retrieval operation with negligible blast radius if invoked inappropriately.

From the tool's definition Tool name and description indicate detection/identification of an installed plugin. 'Erkennt' (German: 'detects') and 'welches Multilingual-Plugin installiert ist' ('which multilingual plugin is installed') describe a querying/inspection operation with no…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ml_detect_plugin safely

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

ml_detect_plugin Allowed

ml_detect_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": {
    "ml_detect_plugin": {}
  }
}

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

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

FAQ

Questions about ml_detect_plugin

What does the ml_detect_plugin tool do? +

Erkennt welches Multilingual-Plugin installiert ist. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ml_detect_plugin? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for ml_detect_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 WordPress MCP Server. Nothing to install.

What risk level is ml_detect_plugin? +

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

Can I rate-limit ml_detect_plugin? +

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

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

ml_detect_plugin is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on WordPress MCP Server, and thousands of servers like it.

This server

All 192 WordPress MCP Server 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 →