This record as markdown: /tools/app-businys-mcp-server/get-profile-page.md
What get_profile_page does on Businys
AI agents call get_profile_page 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 get_profile_page is rated Low
The 'get' prefix and retrieval-oriented description classify this as a Read operation. It accesses profile information without creating, modifying, deleting, executing commands, or incurring financial obligations. The risk is low since profile retrieval is a standard data query with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'get_profile_page' and description states 'Get the ${persona}', indicating retrieval of user/persona profile data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_profile_page 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 get_profile_page, this is the rule to start with:
get_profile_page 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 get_profile_page call is checked against it from then on.
Questions about get_profile_page
Get the ${persona}. 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 get_profile_page: 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.
get_profile_page 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_profile_page 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_profile_page. 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_profile_page 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