my_tool
AI agents call my_tool to retrieve information from Client Onboarding MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The server is explicitly described as 'querying client onboarding status and basic client info' with no modification or deletion capabilities mentioned. Sibling tools are all GET/query operations. The empty description and generic name 'my_tool' introduce uncertainty, but the server context and related tools strongly suggest a read-only operation. Confidence is moderate due to the missing description.
From the tool's definition Tool name 'my_tool' and server description indicate this is a sibling of read-only tools like 'get_client_basic_info', 'get_client_onboarding_status', and 'get_client_facility_limit' on a client onboarding server.
Attacks that exploit this kind of access
my_tool. It is categorised as a Read tool in the Client Onboarding MCP MCP Server, which means it retrieves data without modifying state.
Register the Client Onboarding 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 Client Onboarding MCP. Nothing to install.
my_tool 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 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 Client Onboarding MCP server (rezapars/simple-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 →