Get featured plugins from the store Use when native package install (
AI agents call transfer_plugin-featured to retrieve information from Claude Flow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool fetches/lists featured plugins from a store, which is a read-only retrieval operation with no side effects. Confidence is slightly reduced because the description is truncated ('Use when native package install (') and it's unclear if there is an install/write side effect, but the primary described action is 'Get'.
From the tool's definition 'Get featured plugins from the store' — retrieves/queries a list of featured plugins
Attacks that exploit this kind of access
Get featured plugins from the store Use when native package install (. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for transfer_plugin-featured: 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 Claude Flow. Nothing to install.
transfer_plugin-featured 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-featured 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-featured. 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-featured is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.