AI agents use set_block_data to create or update resources in Pl — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pl environment.
This tool creates or modifies data within a block in Platforma Desktop. The action is reversible (data can be changed again) and does not delete, overwrite irreversibly, move money, or execute arbitrary external code. It fits the Write category. Severity is medium because incorrect data changes could affect project state and dependent blocks, but the effect is localized to a single block and reversible.
From the tool's definition "Set the user-facing data of a block (triggers args derivation and staging)" — the tool explicitly modifies data ('Set') and triggers downstream operations ('args derivation and staging'). The description confirms reversible data modification without deletion.
Attacks that exploit this kind of access
Set the user-facing data of a block (triggers args derivation and staging). It is categorised as a Write tool in the Pl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pl MCP server in PolicyLayer and add a rule for set_block_data: 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 Pl. Nothing to install.
set_block_data 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 set_block_data 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 set_block_data. 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.
set_block_data is provided by the Pl MCP server (@milaboratories/pl-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 →