Low Risk

lookup_context

# Lookup Source Code Context This tool looks up original source code context for a specific line and column position in compiled/minified code. ## Parameters: - **line**: The line number in the compiled code (1-based) - **column**: The column number in the compiled code - **sourceM...

Single-target operation

Part of the Source Map Parser MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call lookup_context to retrieve information from Source Map Parser without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though lookup_context only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-masonchow-source-map-parser-mcp.yaml
tools:
  lookup_context:
    rules:
      - action: allow

See the full Source Map Parser policy for all 3 tools.

Tool Name lookup_context
Category Read
Risk Level Low

Agents calling read-class tools like lookup_context have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the lookup_context tool do? +

# Lookup Source Code Context This tool looks up original source code context for a specific line and column position in compiled/minified code. ## Parameters: - **line**: The line number in the compiled code (1-based) - **column**: The column number in the compiled code - **sourceMapUrl**: The URL of the source map file - **contextLines** (optional): Number of context lines to include before and after the target line (default: 5) ## Returns: - A JSON object containing the source code context snippet with file path, target line info, and surrounding context lines - Returns null if the position cannot be mapped . It is categorised as a Read tool in the Source Map Parser MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lookup_context? +

Add a rule in your Intercept YAML policy under the tools section for lookup_context. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Source Map Parser MCP server.

What risk level is lookup_context? +

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

Can I rate-limit lookup_context? +

Yes. Add a rate_limit block to the lookup_context rule in your Intercept 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 lookup_context completely? +

Set action: deny in the Intercept policy for lookup_context. 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 lookup_context? +

lookup_context is provided by the Source Map Parser MCP server (source-map-parser-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Source Map Parser

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.