New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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.

SERVERTorch-to-Crown SOURCEDiogenes187/Torch-to-Crown
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about get_session_focus

What does the get_session_focus tool do? +

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.

How do I enforce a policy on get_session_focus? +

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.

What risk level is get_session_focus? +

get_session_focus is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_session_focus? +

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.

How do I block get_session_focus completely? +

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.

What MCP server provides get_session_focus? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Torch-to-Crown's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.