param_sweep_setup
AI agents use param_sweep_setup to create or update resources in Flex Sensor Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Flex Sensor Agent environment.
An AI agent can call param_sweep_setup faster than any human can review — one bad instruction and it creates or modifies resources in Flex Sensor Agent by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
param_sweep_setup. It is categorised as a Write tool in the Flex Sensor Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Flex Sensor Agent MCP server in PolicyLayer and add a rule for param_sweep_setup: 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 Flex Sensor Agent. Nothing to install.
param_sweep_setup 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 param_sweep_setup 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 param_sweep_setup. 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.
param_sweep_setup is provided by the Flex Sensor Agent MCP server (tonghui666/flex-sensor-agent-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 →