get_profile
Frank Poncelet's identity: name, role, location, official social links, and biography.
This record as markdown: /tools/com-frankponcelet-profile/get-profile.md
What get_profile does on Profile
AI agents call get_profile to retrieve information from Profile 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 is rated Low
This tool retrieves static biographical and identity information without creating, modifying, deleting, or executing any operations. No reversible writes, irreversible deletes, code execution, or financial transactions occur. The read-only nature of the server and the informational purpose of the tool place it firmly in the Read category with low severity since the data appears to be public profile information.
From the tool's definition Server is explicitly described as 'Read-only MCP server' and tool retrieves 'identity: name, role, location, official social links, and biography' — data about a public profile with no side effects.
Attacks that exploit this kind of access
The rule that runs get_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Profile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_profile, this is the rule to start with:
get_profile 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 Profile, apply this rule, and every get_profile call is checked against it from then on.
Questions about get_profile
Frank Poncelet's identity: name, role, location, official social links, and biography. It is categorised as a Read tool in the Profile MCP Server, which means it retrieves data without modifying state.
Register the Profile MCP server in PolicyLayer and add a rule for get_profile: 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 Profile. Nothing to install.
get_profile 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 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. 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 is provided by the Profile MCP server (https://frankponcelet.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Profile, and thousands of servers like it.
This server
Across the catalogue