Login using API token.
AI agents use mittwald_login_token to create or update resources in Mittwald MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mittwald MCP Server environment.
This tool authenticates a session using an API token, which creates/establishes an authenticated session state. It's a Write operation (creates a session/auth state) rather than purely Read. Misuse could allow unauthorized access to all resources available under that token, but the tool itself is the authentication step rather than a destructive or financial action.
From the tool's definition Login using API token
Attacks that exploit this kind of access
Login using API token. It is categorised as a Write tool in the Mittwald MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mittwald MCP Server MCP server in PolicyLayer and add a rule for mittwald_login_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 Mittwald MCP Server. Nothing to install.
mittwald_login_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 mittwald_login_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 mittwald_login_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.
mittwald_login_token is provided by the Mittwald MCP Server MCP server (mittwald/mcp-server). 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 →