AI agents call info to retrieve information from McFlow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries structural data about projects or workflows without creating, modifying, deleting, or executing anything. It has no side effects and poses minimal risk if invoked by an AI agent, as it only exposes existing information.
From the tool's definition Tool name is 'info' and description states 'Get project or workflow structure information' — the verb 'Get' and lack of any modification language indicates retrieval only.
Attacks that exploit this kind of access
Get project or workflow structure information. It is categorised as a Read tool in the McFlow MCP Server, which means it retrieves data without modifying state.
Register the McFlow MCP server in PolicyLayer and add a rule for info: 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.
info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the info 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 info. 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.
info 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 →