AI agents call my-tool as a supporting operation in Ruflo workflows.
The description provides no actionable information about the tool's behavior, inputs, or outputs. Without any meaningful description, it is impossible to assign a meaningful risk category. Confidence is very low; the tool is classified as Other by default due to insufficient evidence.
From the tool's definition Tool description is 'My custom tool' — entirely uninformative about what the tool does.
Attacks that exploit this kind of access
My custom tool. It is categorised as a Other tool in the Ruflo MCP Server, which means it performs auxiliary operations.
Register the Ruflo MCP server in PolicyLayer and add a rule for my-tool: 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.
my-tool is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the my-tool 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 my-tool. 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.
my-tool 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.
my-tool 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 →