hnalgolia.user.profile
Fetch a HackerNews user profile via the Algolia API — returns username, karma score, and about/bio text (HTML-stripped). Lightweight alternative to the Firebase user endpoint. No auth required. Data: Hacker News (CC BY 3.0).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hnalgolia.user.profile.md
What hnalgolia.user.profile does on Apibase
AI agents call hnalgolia.user.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 |
|---|---|---|---|
username | string | Yes | HackerNews username (case-sensitive). Returns karma score and about/bio text. Examples: "pg", "dang", "tptacek". |
Parameters from the server's own tool schema.
Why hnalgolia.user.profile is rated Low
Retrieves publicly available user profile data with no side effects or modifications.
From the tool's definition Fetch a HackerNews user profile — returns username, karma score, and about/bio text
Attacks that exploit this kind of access
The rule that runs hnalgolia.user.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 hnalgolia.user.profile, this is the rule to start with:
hnalgolia.user.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 hnalgolia.user.profile call is checked against it from then on.
Questions about hnalgolia.user.profile
Fetch a HackerNews user profile via the Algolia API — returns username, karma score, and about/bio text (HTML-stripped). Lightweight alternative to the Firebase user endpoint. No auth required. Data: Hacker News (CC BY 3.0). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
hnalgolia.user.profile accepts 1 parameter: username. Required: username. 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 hnalgolia.user.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.
hnalgolia.user.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 hnalgolia.user.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 hnalgolia.user.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.
hnalgolia.user.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