AI agents use set_plugin_param to create or update resources in Flai — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Flai environment.
This tool modifies a plugin parameter in FL Studio. It creates a reversible change to a parameter value (can be set back), so it falls under Write. Misuse could alter music production settings undesirably, but it's not destructive or irreversible.
From the tool's definition Set a plugin parameter value
Attacks that exploit this kind of access
Set a plugin parameter value. It is categorised as a Write tool in the Flai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Flai MCP server in PolicyLayer and add a rule for set_plugin_param: 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 Flai. Nothing to install.
set_plugin_param 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_plugin_param 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_plugin_param. 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_plugin_param is provided by the Flai MCP server (kaupau/flai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
set_plugin_param is one line of Flai's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →