get_session_focus
Read the referee-authored current scene, phase, and location. The narrating AI receives the public scene summary but not private DM notes and cannot change the scene through this tool.
This record as markdown: /tools/torch-to-crown/get-session-focus.md
What get_session_focus does on Torch-to-Crown
AI agents call get_session_focus to retrieve information from Torch-to-Crown without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_session_focus is rated Low
Even though get_session_focus only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_session_focus safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Torch-to-Crown, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_session_focus, this is the rule to start with:
get_session_focus 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 Torch-to-Crown, apply this rule, and every get_session_focus call is checked against it from then on.
Questions about get_session_focus
Read the referee-authored current scene, phase, and location. The narrating AI receives the public scene summary but not private DM notes and cannot change the scene through this tool. It is categorised as a Read tool in the Torch-to-Crown MCP Server, which means it retrieves data without modifying state.
Register the Torch-to-Crown MCP server in PolicyLayer and add a rule for get_session_focus: 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 Torch-to-Crown. Nothing to install.
get_session_focus 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_session_focus 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_session_focus. 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_session_focus is provided by the Torch-to-Crown MCP server (Diogenes187/Torch-to-Crown). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Torch-to-Crown, and thousands of servers like it.
This server
Across the catalogue