AI agents call read_script to retrieve information from Narrarium without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and inspects existing script data for a book repository. It has no side effects—it neither creates, modifies, deletes, nor executes external operations. The use cases mentioned ('inspect a script before writing prose, or to check what beats are planned') confirm it is purely informational. This is a straightforward Read operation with minimal risk.
From the tool's definition Tool name is 'read_script' and description states it will 'Read an existing scene script and return its meta-language body plus the legend.' The verbs 'Read' and 'return' indicate data retrieval with no modification.
Attacks that exploit this kind of access
Read an existing scene script and return its meta-language body plus the legend. Use this to inspect a script before writing prose, or to check what beats are planned. It is categorised as a Read tool in the Narrarium MCP Server, which means it retrieves data without modifying state.
Register the Narrarium MCP server in PolicyLayer and add a rule for read_script: 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 Narrarium. Nothing to install.
read_script 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 read_script 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 read_script. 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.
read_script is provided by the Narrarium MCP server (narrarium-mcp-server). 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 →