Find a connected client by MAC address or IP address.
AI agents call find_client to retrieve information from API-Central without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a lookup/search operation to retrieve information about a client device on the network. It has no side effects—it does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal; an attacker could only enumerate connected clients, which is a reconnaissance activity. This is consistent with the Read category for query and fetch operations.
From the tool's definition Tool name 'find_client' and description 'Find a connected client by MAC address or IP address' indicate a query operation that retrieves information about network clients without modifying or deleting any data.
Attacks that exploit this kind of access
Find a connected client by MAC address or IP address. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for find_client: 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 API-Central. Nothing to install.
find_client 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 find_client 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 find_client. 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.
find_client is provided by the API-Central MCP server (secure-ssid/centralmcp). 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 →