AI agents call fetch_github_trophies_live to retrieve information from GodProfile MCP Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves GitHub trophy data (achievements/badges) for display on a profile README. Fetching is a read operation with no side effects. The empty description lowers confidence slightly, but the naming pattern and server purpose (generating profile enhancements) strongly indicate this is a data retrieval tool. Low severity because misuse would only retrieve publicly available GitHub profile data.
From the tool's definition Tool name 'fetch_github_trophies_live' uses 'fetch' verb indicating data retrieval. Description is empty, but sibling tools like 'fetch_latest_blog_posts', 'fetch_spotify_now_playing_live', and 'fetch_wakatime_chart_live' all retrieve external data without…
Documented attack patterns abuse exactly the kind of access fetch_github_trophies_live gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GodProfile MCP Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_github_trophies_live:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_github_trophies_live": {}
}
}fetch_github_trophies_live 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.
fetch_github_trophies_live. It is categorised as a Read tool in the GodProfile MCP Toolkit MCP Server, which means it retrieves data without modifying state.
Register the GodProfile MCP Toolkit MCP server in PolicyLayer and add a rule for fetch_github_trophies_live: 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 GodProfile MCP Toolkit. Nothing to install.
fetch_github_trophies_live 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 fetch_github_trophies_live 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 fetch_github_trophies_live. 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.
fetch_github_trophies_live is provided by the GodProfile MCP Toolkit MCP server (luc0-0/godprofile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GodProfile MCP Toolkit, 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.
16 GodProfile MCP Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.