jwt_set_token
Setzt einen JWT Token manuell für die Session
This record as markdown: /tools/c-sakel-wp-mcp-server/jwt-set-token.md
What jwt_set_token does on WordPress MCP Server
AI agents use jwt_set_token to create or update resources in WordPress MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WordPress MCP Server environment.
Why jwt_set_token is rated Medium
This tool writes/sets authentication credentials (JWT token) for the current session. While not destructive, it can be severely misused: an attacker or misbehaving agent could inject a crafted or stolen token to impersonate another user or escalate privileges, making the blast radius high.
From the tool's definition 'Setzt einen JWT Token manuell für die Session' (Sets a JWT token manually for the session)
Attacks that exploit this kind of access
The rule that runs jwt_set_token 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_set_token, this is the rule to start with:
jwt_set_token stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_set_token call is checked against it from then on.
Questions about jwt_set_token
Setzt einen JWT Token manuell für die Session. It is categorised as a Write tool in the WordPress MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for jwt_set_token: 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_set_token is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the jwt_set_token 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_set_token. 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_set_token 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