This is a tool from the github MCP server.\nChecks if a GitHub user has a JSON Resume and returns its information
AI agents call github_check_resume to retrieve information from JSON Resume MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation: it checks for the existence of and retrieves a JSON Resume for a GitHub user. There are no side effects, data modifications, code execution, or destructive operations. The worst-case misuse would be unauthorized information gathering about public resume data, which is a low-severity risk appropriate for a Read classification.
From the tool's definition The tool 'github_check_resume' 'Checks if a GitHub user has a JSON Resume and returns its information' — it retrieves and queries resume data without modifying it.
Documented attack patterns abuse exactly the kind of access github_check_resume gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JSON Resume MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for github_check_resume:
{
"version": "1",
"default": "deny",
"tools": {
"github_check_resume": {}
}
}github_check_resume is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
This is a tool from the github MCP server.\nChecks if a GitHub user has a JSON Resume and returns its information. It is categorised as a Read tool in the JSON Resume MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JSON Resume MCP Server MCP server in PolicyLayer and add a rule for github_check_resume: 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 JSON Resume MCP Server. Nothing to install.
github_check_resume 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_check_resume 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_check_resume. 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_check_resume is provided by the JSON Resume MCP Server MCP server (jsonresume/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JSON Resume 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.
3 JSON Resume MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.