Say hello from Inject Bender! Meet Skippie and Odin.
AI agents call bender_hello to retrieve information from Inject Bender without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely returns a greeting message. It retrieves or displays static information about the Inject Bender service (introducing mascots Skippie and Odin) without any side effects, data modification, code execution, or resource commitment. It is a read-only informational tool with minimal security risk.
From the tool's definition Tool name 'bender_hello' and description 'Say hello from Inject Bender! Meet Skippie and Odin.' indicate a simple greeting/informational function with no data modification, deletion, execution, or financial impact.
Attacks that exploit this kind of access
Say hello from Inject Bender! Meet Skippie and Odin. It is categorised as a Read tool in the Inject Bender MCP Server, which means it retrieves data without modifying state.
Register the Inject Bender MCP server in PolicyLayer and add a rule for bender_hello: 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 Inject Bender. Nothing to install.
bender_hello 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 bender_hello 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 bender_hello. 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.
bender_hello is provided by the Inject Bender MCP server (jaspertvdm/mcp-inject-bender). 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 →