Get information about the Georgia Tech research repository
AI agents call get_repository_info to retrieve information from Georgia Tech MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries information from a research repository without performing any side effects, modifications, or state changes. It aligns with the Read category pattern (get, fetch, search). Low severity reflects minimal risk—an AI agent misusing this tool would only retrieve repository data that is presumably already intended for access, with no ability to modify, delete, or execute operations.
From the tool's definition Tool name 'get_repository_info' and description 'Get information about the Georgia Tech research repository' indicate a retrieval/query operation.
Attacks that exploit this kind of access
Get information about the Georgia Tech research repository. It is categorised as a Read tool in the Georgia Tech MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Georgia Tech MCP Server MCP server in PolicyLayer and add a rule for get_repository_info: 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 Georgia Tech MCP Server. Nothing to install.
get_repository_info 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_repository_info 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_repository_info. 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_repository_info is provided by the Georgia Tech MCP Server MCP server (wondermuttt/gtmcp). 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 →