This record as markdown: /tools/sagemcp-sagemcp/github-get-user-activity.md
What github_get_user_activity does on Sage MCP
AI agents call github_get_user_activity to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why github_get_user_activity is rated Low
This tool retrieves user activity data from GitHub without modifying, deleting, or executing any operations. It is a read-only query operation with minimal blast radius. Even if misused by an agent, the worst outcome would be unauthorized access to publicly or semi-publicly available user information, which poses low risk compared to write or destructive operations.
From the tool's definition Tool name and description indicate retrieval of user activity/information: 'Get user' suggests a query operation that fetches data. The verb 'get' paired with 'user_activity' clearly indicates data retrieval without modification or side effects.
Attacks that exploit this kind of access
The rule that runs github_get_user_activity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_get_user_activity, this is the rule to start with:
github_get_user_activity is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every github_get_user_activity call is checked against it from then on.
Questions about github_get_user_activity
Get user. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for github_get_user_activity: 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 Sage MCP. Nothing to install.
github_get_user_activity 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_get_user_activity 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_get_user_activity. 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_get_user_activity is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sage, and thousands of servers like it.
This server
Across the catalogue