Find execution flows impacted by file changes. Args: changed_files: Comma-separated file paths.
AI agents call get_affected_flows to retrieve information from Qualixar/superlocalmemory 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 information about which execution flows are affected by specified file changes. It takes file paths as input and returns analysis results without modifying, deleting, or executing any code. The operation is read-only with no side effects, making it a Read category tool.
From the tool's definition Tool name 'get_affected_flows' and description 'Find execution flows impacted by file changes' indicate a query/retrieval operation that analyzes and returns information about code dependencies and impact.
Documented attack patterns abuse exactly the kind of access get_affected_flows gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qualixar/superlocalmemory, and nothing reaches the server without passing your rules. This is the rule we recommend for get_affected_flows:
{
"version": "1",
"default": "deny",
"tools": {
"get_affected_flows": {}
}
}get_affected_flows 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.
Find execution flows impacted by file changes. Args: changed_files: Comma-separated file paths. It is categorised as a Read tool in the Qualixar/superlocalmemory MCP Server, which means it retrieves data without modifying state.
Register the Qualixar/superlocalmemory MCP server in PolicyLayer and add a rule for get_affected_flows: 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 Qualixar/superlocalmemory. Nothing to install.
get_affected_flows 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_affected_flows 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_affected_flows. 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_affected_flows is provided by the Qualixar/superlocalmemory MCP server (qualixar/superlocalmemory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 59 Qualixar/superlocalmemory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
59 Qualixar/superlocalmemory tools catalogued and risk-classified — across an index of 42,500+ MCP servers.