load_session_profile
Reads ~/.tdmcp/session-profile.json (or a custom path) and returns a unified JSON
This record as markdown: /tools/hybridlabor-api-aos/load-session-profile.md
What load_session_profile does on Aos
AI agents call load_session_profile to retrieve information from Aos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why load_session_profile is rated Low
This tool queries and retrieves configuration data from a JSON file. It performs a read-only operation that retrieves existing data without creating, modifying, deleting, or executing any commands. The action is passive and informational, consistent with the 'Read' category for data retrieval tools.
From the tool's definition Tool name 'load_session_profile' and description 'Reads ~/.tdmcp/session-profile.json (or a custom path) and returns a unified JSON' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs load_session_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For load_session_profile, this is the rule to start with:
load_session_profile 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 Aos, apply this rule, and every load_session_profile call is checked against it from then on.
Questions about load_session_profile
Reads ~/.tdmcp/session-profile.json (or a custom path) and returns a unified JSON. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.
Register the Aos MCP server in PolicyLayer and add a rule for load_session_profile: 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 Aos. Nothing to install.
load_session_profile 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 load_session_profile 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 load_session_profile. 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.
load_session_profile is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue