This record as markdown: /tools/app-businys-mcp-server/client-name.md
What client_name does on Businys
AI agents call client_name to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why client_name is rated Low
This tool retrieves or queries client name data with no side effects. It fits the Read category pattern of data retrieval without modification. Low severity due to limited blast radius—exposing a client name alone poses minimal risk compared to financial, destructive, or execution capabilities. Confidence is high despite minimal description because the pattern is consistent with a data lookup utility.
From the tool's definition Tool named 'client_name' with description 'Client' suggests retrieval of client information. No action verbs indicating modification, deletion, or execution are present.
Attacks that exploit this kind of access
The rule that runs client_name safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For client_name, this is the rule to start with:
client_name is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every client_name call is checked against it from then on.
Questions about client_name
Client. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.
Register the Businys MCP server in PolicyLayer and add a rule for client_name: 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 Businys. Nothing to install.
client_name 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 client_name 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 client_name. 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.
client_name is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue