AI agents use configure_tracking to create or update resources in McFlow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your McFlow environment.
This tool modifies workflow tracking settings globally, which affects how workflows behave and log data. It is reversible (settings can be reconfigured), so it falls under Write rather than Execute or Destructive. The medium severity accounts for the fact that misconfiguration could impact workflow visibility, debugging, or compliance, but does not directly execute code or delete data.
From the tool's definition Tool name 'configure_tracking' and description 'Configure global tracking settings for workflows' indicate modification of workflow configuration. The verb 'configure' implies changing settings rather than merely reading them.
Attacks that exploit this kind of access
Configure global tracking settings for workflows. It is categorised as a Write tool in the McFlow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the McFlow MCP server in PolicyLayer and add a rule for configure_tracking: 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 McFlow. Nothing to install.
configure_tracking 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 configure_tracking 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 configure_tracking. 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.
configure_tracking is provided by the McFlow MCP server (mckinleymedia/mcflow-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 →