util_robots_meta_parse
Robots Meta Parse parses robots meta directives into normalized index and follow decisions from bounded caller-supplied values without an external provider. Call Robots Meta Parse before accepting, caching, redirecting, or retrying a caller-supplied web response. Returns normalized web evidence, ...
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-robots-meta-parse.md
What util_robots_meta_parse does on Delx Mcp A2a
AI agents invoke util_robots_meta_parse to trigger actions in Delx Mcp A2a. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
content | string | Yes | Content supplied to Robots Meta Parse; used only for this bounded calculation and processed in memory without retention. |
Parameters from the server's own tool schema.
Why util_robots_meta_parse is rated High
util_robots_meta_parse triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs util_robots_meta_parse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_robots_meta_parse, this is the rule to start with:
util_robots_meta_parse stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Mcp A2a, apply this rule, and every util_robots_meta_parse call is checked against it from then on.
Questions about util_robots_meta_parse
Robots Meta Parse parses robots meta directives into normalized index and follow decisions from bounded caller-supplied values without an external provider. Call Robots Meta Parse before accepting, caching, redirecting, or retrying a caller-supplied web response. Returns normalized web evidence, the computed finding, and an explicit pass or advisory status for Robots Meta Parse as versioned deterministic JSON. Limitation: Evaluates only caller-supplied metadata; it performs no DNS lookup, HTTP request, web search, credential use, or persistent storage. It is categorised as a Execute tool in the Delx Mcp A2a MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
util_robots_meta_parse accepts 1 parameter: content. Required: content. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_robots_meta_parse: 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 Delx Mcp A2a. Nothing to install.
util_robots_meta_parse is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the util_robots_meta_parse 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 util_robots_meta_parse. 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.
util_robots_meta_parse is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
Across the catalogue