This record as markdown: /tools/io-github-aibtcdev-mcp-server/nostr-set-profile.md
What nostr_set_profile does on Aibtc
AI agents use nostr_set_profile to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.
Why nostr_set_profile is rated Medium
The tool performs a reversible write operation that modifies profile data. It is not Read (no query/retrieval), not Destructive (changes are reversible), not Execute (no code/shell execution), and not Financial (no monetary transactions). The medium severity reflects that unauthorized profile modifications could impact reputation or access control, but are not irreversible.
From the tool's definition Tool name contains 'set' and description states 'Update the agent', indicating modification of existing data.
Attacks that exploit this kind of access
The rule that runs nostr_set_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nostr_set_profile, this is the rule to start with:
nostr_set_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 Aibtc, apply this rule, and every nostr_set_profile call is checked against it from then on.
Questions about nostr_set_profile
Update the agent. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aibtc MCP server in PolicyLayer and add a rule for nostr_set_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 Aibtc. Nothing to install.
nostr_set_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 nostr_set_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 nostr_set_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.
nostr_set_profile is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue