jwt_token_info
Zeigt Informationen zum aktuellen JWT Token
This record as markdown: /tools/c-sakel-wp-mcp-server/jwt-token-info.md
What jwt_token_info does on WordPress MCP Server
AI agents call jwt_token_info 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.
Why jwt_token_info is rated Low
This tool retrieves and displays information about a JWT token—a read-only operation with no side effects. It does not create, modify, delete, or execute any actions. The blast radius is minimal as it only exposes token details that an authenticated user would already have access to.
From the tool's definition Tool name 'jwt_token_info' and description 'Zeigt Informationen zum aktuellen JWT Token' (Shows information about the current JWT token) indicate retrieval/query of token metadata without modification.
Attacks that exploit this kind of access
The rule that runs jwt_token_info 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_token_info, this is the rule to start with:
jwt_token_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every jwt_token_info call is checked against it from then on.
Questions about jwt_token_info
Zeigt Informationen zum aktuellen JWT Token. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for jwt_token_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 WordPress MCP Server. Nothing to install.
jwt_token_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 jwt_token_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 jwt_token_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.
jwt_token_info 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.
More on WordPress MCP Server, and thousands of servers like it.
This server
Across the catalogue