Saare developers ki activity log dekho — kaun, kab, kya kiya (branch aur time filter supported)
AI agents call get_activity_log to retrieve information from Universal Dev MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries historical activity records without modifying, deleting, or executing any operations. It is a pure read operation that returns audit/log data for viewing purposes, with no side effects on the system.
From the tool's definition Tool name 'get_activity_log' and description 'Saare developers ki activity log dekho — kaun, kab, kya kiya' indicates retrieval of activity logs (who, when, what actions); filters support (branch and time) are query parameters only.
Attacks that exploit this kind of access
Saare developers ki activity log dekho — kaun, kab, kya kiya (branch aur time filter supported). It is categorised as a Read tool in the Universal Dev MCP MCP Server, which means it retrieves data without modifying state.
Register the Universal Dev MCP server in PolicyLayer and add a rule for get_activity_log: 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 Universal Dev MCP. Nothing to install.
get_activity_log 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_activity_log 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_activity_log. 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_activity_log is provided by the Universal Dev MCP server (kallusuvaidyam/universal_mcp). 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 →