lctx_fetch_and_index · Logica Context MCP: Risk & Policy

WHAT IT DOES

What lctx_fetch_and_index does on Logica Context

AI agents use lctx_fetch_and_index to create or update resources in Logica Context — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Logica Context environment.

WHY IT NEEDS A POLICY

Why lctx_fetch_and_index needs a policy

This tool fetches external content and writes/indexes it into the persistent memory store. The primary side effect is creating or updating indexed content in the system. While it reads from a URL, the meaningful action is indexing (writing) the result into the knowledge base. It is reversible in principle (content can be purged), so Destructive does not apply.

From the tool's definition Fetch a URL, convert HTML to markdown, and index the content

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lctx_fetch_and_index Rate-limited

lctx_fetch_and_index stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lctx_fetch_and_index": {
      "limits": [
        {
          "counter": "lctx_fetch_and_index_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Logica Context, so you can run agents against it safely.

FAQ

Questions about lctx_fetch_and_index

What does the lctx_fetch_and_index tool do? +

Fetch a URL, convert HTML to markdown, and index the content. Cached for 24 hours. It is categorised as a Write tool in the Logica Context MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lctx_fetch_and_index? +

Register the Logica Context MCP server in PolicyLayer and add a rule for lctx_fetch_and_index: 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 Logica Context. Nothing to install.

What risk level is lctx_fetch_and_index? +

lctx_fetch_and_index is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit lctx_fetch_and_index? +

Yes. Add a rate_limit block to the lctx_fetch_and_index 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 lctx_fetch_and_index completely? +

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

lctx_fetch_and_index is provided by the Logica Context MCP server (rovemark/logica-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.