My tool description
AI agents call my-tool as a supporting operation in PatternFly MCP Server workflows.
The description is entirely uninformative ('My tool description' is a placeholder). Without any evidence of read, write, execute, destructive, or financial operations, this cannot be reliably classified. Defaulting to Other with very low confidence due to lack of meaningful description.
From the tool's definition Tool name 'my-tool' and description 'My tool description' are both placeholder/generic text with no meaningful information about what the tool actually does.
Attacks that exploit this kind of access
My tool description. It is categorised as a Other tool in the PatternFly MCP Server MCP Server, which means it performs auxiliary operations.
Register the PatternFly MCP Server 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 PatternFly MCP Server. 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 PatternFly MCP Server MCP server (patternfly/patternfly-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 →