mark_discovered_url_processed · Langfuse Observability MCP

WHAT IT DOES

What mark_discovered_url_processed does on Langfuse Observability

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

WHY IT NEEDS A POLICY

Why mark_discovered_url_processed needs a policy

This tool performs a state modification (marking a URL as processed) but the change is reversible and non-destructive. It updates metadata/status fields rather than creating/deleting content. The data modification is audit-logged and idempotent, characteristics of a Write operation. Blast radius is minimal—only internal tracking state is affected, no external systems or data loss involved.

From the tool's definition Tool description indicates 'Mark a single discovered URL as processed' which updates state by setting 'processed_at to the current timestamp and stores the result for audit trail'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark_discovered_url_processed Rate-limited

mark_discovered_url_processed 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": {
    "mark_discovered_url_processed": {
      "limits": [
        {
          "counter": "mark_discovered_url_processed_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 Langfuse Observability, so you can run agents against it safely.

FAQ

Questions about mark_discovered_url_processed

What does the mark_discovered_url_processed tool do? +

Mark a single discovered URL as processed after the agent has handled it. Sets processed_at to the current timestamp and stores the result for audit trail. Idempotent — calling on an already-processed URL updates the fields. Use cases: - Mark a URL as. It is categorised as a Write tool in the Langfuse Observability MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mark_discovered_url_processed? +

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

What risk level is mark_discovered_url_processed? +

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

Can I rate-limit mark_discovered_url_processed? +

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

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

mark_discovered_url_processed is provided by the Langfuse Observability MCP server (langfuse-observability-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.