Replace a question (PUT).
AI agents use blawx_question_update to create or update resources in Blawx MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blawx MCP Server environment.
This tool creates or modifies data reversibly by replacing question objects in a rule-based logic system. While it affects stored data, the operation is not irreversible (questions can be updated again or restored), and it does not execute arbitrary code, delete data permanently, or move financial assets.
From the tool's definition Tool name indicates 'update' operation (PUT request); description states 'Replace a question', which modifies existing data in the Blawx system.
Attacks that exploit this kind of access
Replace a question (PUT). It is categorised as a Write tool in the Blawx MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blawx MCP Server MCP server in PolicyLayer and add a rule for blawx_question_update: 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 Blawx MCP Server. Nothing to install.
blawx_question_update 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 blawx_question_update 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 blawx_question_update. 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.
blawx_question_update is provided by the Blawx MCP Server MCP server (lexpedite/blawx_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 →