Inspect a local notebook under AWS_NOTEBOOK_RUNNER_ROOT.
AI agents call inspect_notebook to retrieve information from AWS Notebook Runner MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs introspection of notebook files within a constrained local directory (AWS_NOTEBOOK_RUNNER_ROOT). It has no side effects, does not modify data, does not execute code, does not incur costs, and does not delete anything. The worst case of misuse is information disclosure about notebook structure or contents, which is a low-severity risk.
From the tool's definition Tool description states 'Inspect a local notebook' which is a read-only operation that retrieves and examines notebook metadata or contents without modification, deletion, or execution.
Attacks that exploit this kind of access
Inspect a local notebook under AWS_NOTEBOOK_RUNNER_ROOT. It is categorised as a Read tool in the AWS Notebook Runner MCP MCP Server, which means it retrieves data without modifying state.
Register the AWS Notebook Runner MCP server in PolicyLayer and add a rule for inspect_notebook: 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 AWS Notebook Runner MCP. Nothing to install.
inspect_notebook 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 inspect_notebook 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 inspect_notebook. 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.
inspect_notebook is provided by the AWS Notebook Runner MCP server (yummytastycode/aws-notebook-runner-mcp). 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 →