get_my_profile
A read tool on the 1point3acres Toolkit MCP server.
This record as markdown: /tools/1point3acres-toolkit/get-my-profile.md
What get_my_profile does on 1point3acres Toolkit
AI agents call get_my_profile to retrieve information from 1point3acres Toolkit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_my_profile is rated Low
This tool retrieves profile information about the authenticated user with no side effects. It performs data retrieval only, matching the Read category definition. Severity is low because profile data exposure is limited in scope compared to other LinkedIn automation risks on this server (posting, connecting, messaging).
From the tool's definition Tool name 'get_my_profile' indicates a retrieval operation. The function name follows read-pattern conventions (get_*). Server context shows tools like 'get_feed', 'get_inbox', 'get_company_profile' which are clearly read operations.
Attacks that exploit this kind of access
The rule that runs get_my_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1point3acres Toolkit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_my_profile, this is the rule to start with:
get_my_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 1point3acres Toolkit, apply this rule, and every get_my_profile call is checked against it from then on.
Questions about get_my_profile
get_my_profile is a read tool on the 1point3acres Toolkit MCP server. It is categorised as a Read tool in the 1point3acres Toolkit MCP Server, which means it retrieves data without modifying state.
Register the 1point3acres Toolkit MCP server in PolicyLayer and add a rule for get_my_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 1point3acres Toolkit. Nothing to install.
get_my_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_my_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_my_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_my_profile is provided by the 1point3acres Toolkit MCP server (vivian-labs/1point3acres-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1point3acres Toolkit, and thousands of servers like it.
This server
Across the catalogue