jwt_check_plugin

Prüft ob ein JWT Authentication 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/jwt-check-plugin.md

WHAT IT DOES

What jwt_check_plugin does on WordPress MCP Server

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

This tool retrieves information about whether a specific plugin is installed on the WordPress site. It performs a read-only check without creating, modifying, deleting, or executing any operations. The minimal severity is appropriate since plugin detection poses no direct risk to the system—it merely gathers status information.

From the tool's definition Tool name 'jwt_check_plugin' and description 'Prüft ob ein JWT Authentication Plugin installiert ist' (Checks if a JWT Authentication Plugin is installed) indicate a query/detection operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs jwt_check_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 jwt_check_plugin, this is the rule to start with:

jwt_check_plugin Allowed

jwt_check_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": {
    "jwt_check_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 jwt_check_plugin call is checked against it from then on.

FAQ

Questions about jwt_check_plugin

What does the jwt_check_plugin tool do? +

Prüft ob ein JWT Authentication 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 jwt_check_plugin? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for jwt_check_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 jwt_check_plugin? +

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

Can I rate-limit jwt_check_plugin? +

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

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

jwt_check_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

The MCP Attack Database →

Guides

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