Create a Mealie API token for the current user.
AI agents use create_user_api_token to create or update resources in Mealie MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mealie MCP Server environment.
This tool creates an API token, which is a Write operation (creates a new credential). However, the severity is high because a newly created API token could grant persistent access to the Mealie system, potentially enabling an attacker to perform further actions including reading sensitive data, modifying recipes/meal plans, or escalating privileges. Credential creation has significant security implications.
From the tool's definition 'Create a Mealie API token for the current user'
Attacks that exploit this kind of access
Create a Mealie API token for the current user. It is categorised as a Write tool in the Mealie MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mealie MCP Server MCP server in PolicyLayer and add a rule for create_user_api_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 Mealie MCP Server. Nothing to install.
create_user_api_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 create_user_api_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 create_user_api_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.
create_user_api_token is provided by the Mealie MCP Server MCP server (nikopol666/mealie-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →