get_career
Career timeline chapters (Air Force → education → ING → Web3). Optionally filter by era or chapter title.
This record as markdown: /tools/com-frankponcelet-profile/get-career.md
What get_career does on Profile
AI agents call get_career 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
era | string | — | Case-insensitive substring matched against a chapter's era or title (e.g. 'ING', 'Blockchain', 'Chapter II'). |
Parameters from the server's own tool schema.
Why get_career is rated Low
This tool only queries and retrieves historical career information about Frank Poncelet. It has no side effects, does not modify any data, and does not trigger external operations. It is a straightforward read operation that fits the 'Read' category with low severity since exposure of this information poses minimal risk.
From the tool's definition Tool name is 'get_career' and server is described as 'Read-only MCP server'. The tool retrieves career timeline chapters with optional filtering; no modification, deletion, or execution capabilities are described.
Attacks that exploit this kind of access
The rule that runs get_career 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_career, this is the rule to start with:
get_career 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_career call is checked against it from then on.
Questions about get_career
Career timeline chapters (Air Force → education → ING → Web3). Optionally filter by era or chapter title. It is categorised as a Read tool in the Profile MCP Server, which means it retrieves data without modifying state.
get_career accepts 1 parameter: era. The full parameter table on this page comes from the server's own tool schema.
Register the Profile MCP server in PolicyLayer and add a rule for get_career: 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_career 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_career 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_career. 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_career 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