Low Risk

get_repository

Get a GitHub repository by owner and repository name.

How to control get_repository ↓

What get_repository does on TypeSpec MCP Server

AI agents call get_repository to retrieve information from TypeSpec MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_repository needs a policy

This tool queries GitHub to retrieve repository metadata or information by owner and name parameters. It performs no modifications, deletions, or external operations—purely a read operation. No financial impact, no code execution. Severity is low because repository metadata is typically public or authorized information with minimal blast radius if an AI agent retrieves unintended repositories.

From the tool's definition Tool name 'get_repository' and description 'Get a GitHub repository by owner and repository name' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_repository gives an agent:

How to control get_repository

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_repository": {}
  }
}

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

  1. Create a free account and register TypeSpec MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_repository

What does the get_repository tool do? +

Get a GitHub repository by owner and repository name. It is categorised as a Read tool in the TypeSpec MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_repository? +

Register the TypeSpec MCP Server MCP server in PolicyLayer and add a rule for get_repository: 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 TypeSpec MCP Server. Nothing to install.

What risk level is get_repository? +

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

Can I rate-limit get_repository? +

Yes. Add a rate_limit block to the get_repository 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_repository completely? +

Set action: deny in the PolicyLayer policy for get_repository. 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_repository? +

get_repository is provided by the TypeSpec MCP Server MCP server (microsoft/typespec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TypeSpec MCP Server tool call.

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

Free to start. No card required.

28 TypeSpec MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.