update_my_profile
Update your profile. One action per call.
This record as markdown: /tools/launch-on-basis-mcp-ts/update-my-profile.md
What update_my_profile does on Basis MCP Server
AI agents use update_my_profile to create or update resources in Basis MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Basis MCP Server environment.
Why update_my_profile is rated Medium
This tool modifies user profile information in a reversible manner. It creates or updates data without deleting it irreversibly, without executing arbitrary code, and without moving funds. While the server provides financial and trading tools, this specific tool is limited to profile metadata updates, making it a straightforward Write operation with low severity due to its narrow scope and reversibility.
From the tool's definition Tool name 'update_my_profile' and description 'Update your profile' indicate modification of user profile data. The phrase 'One action per call' suggests a single, reversible write operation.
Attacks that exploit this kind of access
The rule that runs update_my_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_my_profile, this is the rule to start with:
update_my_profile stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every update_my_profile call is checked against it from then on.
Questions about update_my_profile
Update your profile. One action per call. It is categorised as a Write tool in the Basis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for update_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 Basis MCP Server. Nothing to install.
update_my_profile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_my_profile is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Basis MCP Server, and thousands of servers like it.
This server
Across the catalogue