Return the currently-configured output directory for this session.
AI agents call get_output_directory to retrieve information from MCP GeneLab Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves session configuration information (the output directory path) without creating, modifying, deleting, or executing any operations. It is a read-only query with no blast radius if misused by an AI agent—at worst, it reveals the directory path being used for the session.
From the tool's definition Tool name 'get_output_directory' and description 'Return the currently-configured output directory for this session' indicate a simple query that retrieves configuration state without modification or side effects.
Attacks that exploit this kind of access
Return the currently-configured output directory for this session. It is categorised as a Read tool in the MCP GeneLab Server MCP Server, which means it retrieves data without modifying state.
Register the MCP GeneLab Server MCP server in PolicyLayer and add a rule for get_output_directory: 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 MCP GeneLab Server. Nothing to install.
get_output_directory 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_output_directory 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_output_directory. 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_output_directory is provided by the MCP GeneLab Server MCP server (sbl-sdsc/mcp-genelab). 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 →