github_user_pinned
List a GitHub user's pinned repositories. Returns the repositories a user pinned on their public profile (showcase signal). Empty when the user pinned nothing.
This record as markdown: /tools/crawlora-mcp/github-user-pinned.md
What github_user_pinned does on Crawlora
AI agents call github_user_pinned to retrieve information from Crawlora 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 | GitHub username |
Parameters from the server's own tool schema.
Why github_user_pinned is rated Low
This tool retrieves publicly available profile information from GitHub without side effects. It queries and returns data (pinned repositories) with no capability to modify, execute code, or delete anything. The blast radius of misuse is minimal—an agent could only over-query or spam requests, not compromise data or systems.
From the tool's definition Tool 'List a GitHub user's pinned repositories' and 'Returns the repositories a user pinned on their public profile' indicate data retrieval only. No modification, deletion, or execution mentioned.
Attacks that exploit this kind of access
The rule that runs github_user_pinned safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_user_pinned, this is the rule to start with:
github_user_pinned 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 Crawlora, apply this rule, and every github_user_pinned call is checked against it from then on.
Questions about github_user_pinned
List a GitHub user's pinned repositories. Returns the repositories a user pinned on their public profile (showcase signal). Empty when the user pinned nothing. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
github_user_pinned accepts 1 parameter: username. Required: username. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for github_user_pinned: 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 Crawlora. Nothing to install.
github_user_pinned 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 github_user_pinned 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 github_user_pinned. 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.
github_user_pinned is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue