Fetch detailed info (usage, bandwidth, auth) for a single client by MAC address.
AI agents call get_client_details 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 queries and retrieves client information (usage statistics, bandwidth metrics, authentication details) without modifying, deleting, or executing any operations. The verb 'Fetch' and the enumeration of read-only data types (usage, bandwidth, auth metadata) confirm this is a Read operation with low severity—misuse would only expose network data without causing operational harm.
From the tool's definition Tool name 'get_client_details' and description 'Fetch detailed info (usage, bandwidth, auth) for a single client by MAC address' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch detailed info (usage, bandwidth, auth) for a single client by MAC 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 get_client_details: 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.
get_client_details 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 get_client_details 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 get_client_details. 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.
get_client_details 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 →