AI agents call transfer_plugin-info to retrieve information from Ruflo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool description indicates it retrieves/reads plugin information. The name 'transfer_plugin-info' is slightly ambiguous but the description clarifies it is a read/get operation. The description is truncated ('Use when native package install ('), which slightly lowers confidence, but the primary stated action is informational retrieval. Severity is low as reading plugin metadata has minimal blast radius.
From the tool's definition 'Get detailed info about a plugin' — retrieves informational data about a plugin with no stated side effects
Attacks that exploit this kind of access
Get detailed info about a plugin Use when native package install (. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo MCP server in PolicyLayer and add a rule for transfer_plugin-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 Ruflo. Nothing to install.
transfer_plugin-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 transfer_plugin-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 transfer_plugin-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.
transfer_plugin-info is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
transfer_plugin-info is one line of Ruflo'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 →