Get list of actively edited files in recent minutes.
AI agents call get_active_files to retrieve information from Session Buddy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple read operation to list recently edited files. It has no side effects, does not execute code, does not modify or delete data, and does not involve financial operations. The blast radius of misuse is minimal—an agent could only learn which files were recently edited, which is low-sensitivity metadata in a local session context.
From the tool's definition Tool name 'get_active_files' and description 'Get list of actively edited files in recent minutes' indicates a query operation that retrieves metadata about file activity without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get list of actively edited files in recent minutes. It is categorised as a Read tool in the Session Buddy MCP Server, which means it retrieves data without modifying state.
Register the Session Buddy MCP server in PolicyLayer and add a rule for get_active_files: 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 Session Buddy. Nothing to install.
get_active_files 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_active_files 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_active_files. 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_active_files is provided by the Session Buddy MCP server (lesleslie/session-buddy). 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 →