AI agents use magnyxa_set_token to create or update resources in Magnyxa — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Magnyxa environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
token | string | Yes | WebUIで発行したMagnyxa MCPトークン（magnyxa_mcp_で始まる） |
Parameters from the server's own tool schema.
This tool writes/sets authentication credentials (a one-time-use token) into the system state. While not destructive or financial, it modifies the configuration in a way that affects subsequent operations and access control. The high severity reflects that improper token configuration could grant unauthorized access or interfere with legitimate authentication flows.
From the tool's definition Tool description states 'Magnyxa MCPトークンを設定します' (setting/configuring Magnyxa MCP token). The verb '設定します' (to set/configure) indicates a persistent state modification. Token configuration is a write operation that modifies authentication state.
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
Magnyxa MCPトークンを設定します。WebUIで発行したトークン（magnyxa_mcp_から始まる文字列）を入力してください。このトークンは1回のみ使用できます。. It is categorised as a Write tool in the Magnyxa MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
magnyxa_set_token accepts 1 parameter: token. Required: token. The full parameter table on this page comes from the server's own tool schema.
Register the Magnyxa MCP server in PolicyLayer and add a rule for magnyxa_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 Magnyxa. Nothing to install.
magnyxa_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 magnyxa_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 magnyxa_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.
magnyxa_set_token is provided by the Magnyxa MCP server (@zelklab/magnyxa-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 →