Get repositories belonging to the authenticated user
AI agents call get_my_repos to retrieve information from GitHub MCP TypeScript SDK Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of repositories owned by the authenticated user. It performs a query operation that has no side effects—it does not create, modify, delete, or execute any code. The action is purely informational, making it a Read category tool with low severity risk since misuse would only expose information the user already has access to.
From the tool's definition Tool name 'get_my_repos' and description 'Get repositories belonging to the authenticated user' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get repositories belonging to the authenticated user. It is categorised as a Read tool in the GitHub MCP TypeScript SDK Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP TypeScript SDK Server MCP server in PolicyLayer and add a rule for get_my_repos: 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 GitHub MCP TypeScript SDK Server. Nothing to install.
get_my_repos 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 get_my_repos 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 get_my_repos. 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.
get_my_repos is provided by the GitHub MCP TypeScript SDK Server MCP server (om-shree-0709/github-mcp-ts-sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →