get-profile

THE RISK

Low Risk

Why get-profile needs a policy

This tool retrieves profile information without side effects, making it a Read operation. The severity is low because accessing one's own profile data poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'get-profile' and description 'Get your Bluesky profile' indicate data retrieval only. No modification, execution, or deletion of data occurs.

Documented attack patterns abuse exactly the kind of access get-profile gives an agent:

POLICY

How to control get-profile

PolicyLayer is an MCP gateway — it sits between your AI agents and Bluesky, and nothing reaches the server without passing your rules. This is the rule we recommend for get-profile:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-profile": {}
  }
}

get-profile is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Bluesky — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Bluesky tools

Destructive delete-post Delete one of your posts Destructive unrepost Remove your repost Write create-post Create a new post on Bluesky Write like-post Like a post Write login Login to Bluesky using credentials from .env file or provided parameters Write repost Repost someone Write unlike-post Remove your like from a post Read get-post Get a specific post by URI

All 11 Bluesky tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get-profile

What does the get-profile tool do? +

Get your Bluesky profile. It is categorised as a Read tool in the Bluesky MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-profile? +

Register the Bluesky 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 Bluesky. Nothing to install.

What risk level is get-profile? +

get-profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-profile? +

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.

How do I block get-profile completely? +

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.

What MCP server provides get-profile? +

get-profile is provided by the Bluesky MCP server (semioz/bluesky-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Bluesky tool call.

Start from Bluesky, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →