social.bluesky.profile
Get a Bluesky user profile — display name, bio, avatar URL, follower/following/post counts, account creation date. Lookup by handle (e.g. "jay.bsky.team") (AT Protocol / Bluesky)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/social.bluesky.profile.md
What social.bluesky.profile does on Apibase
AI agents call social.bluesky.profile to retrieve information from Apibase 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 |
|---|---|---|---|
handle | string | Yes | Bluesky handle (e.g. "jay.bsky.team", "pfrazee.com", "apibase.bsky.social") |
Parameters from the server's own tool schema.
Why social.bluesky.profile is rated Low
Tool retrieves public profile metadata with no side effects or data modification capabilities.
From the tool's definition Get a Bluesky user profile, display name, bio, avatar URL, follower counts
Attacks that exploit this kind of access
The rule that runs social.bluesky.profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For social.bluesky.profile, this is the rule to start with:
social.bluesky.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 Apibase, apply this rule, and every social.bluesky.profile call is checked against it from then on.
Questions about social.bluesky.profile
Get a Bluesky user profile — display name, bio, avatar URL, follower/following/post counts, account creation date. Lookup by handle (e.g. "jay.bsky.team") (AT Protocol / Bluesky). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
social.bluesky.profile accepts 1 parameter: handle. Required: handle. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for social.bluesky.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 Apibase. Nothing to install.
social.bluesky.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 social.bluesky.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 social.bluesky.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.
social.bluesky.profile is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue