util_avg_entry

Volume-weighted average entry across fill price/size pairs

SERVERDelx Mcp A2a SOURCEhttps://api.delx.ai/v1/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-avg-entry.md

WHAT IT DOES

What util_avg_entry does on Delx Mcp A2a

AI agents call util_avg_entry to retrieve information from Delx Mcp A2a without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`fills`	array	Yes	Input field: fills.

Parameters from the server's own tool schema.

RISK

Why util_avg_entry is rated Low

Even though util_avg_entry only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs util_avg_entry 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_avg_entry, this is the rule to start with:

util_avg_entry Allowed

util_avg_entry is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "util_avg_entry": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Delx Mcp A2a, apply this rule, and every util_avg_entry call is checked against it from then on.

FAQ

Questions about util_avg_entry

What does the util_avg_entry tool do? +

Volume-weighted average entry across fill price/size pairs. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.

What parameters does util_avg_entry accept? +

util_avg_entry accepts 1 parameter: fills. Required: fills. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on util_avg_entry? +

Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_avg_entry: 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.

What risk level is util_avg_entry? +

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

Can I rate-limit util_avg_entry? +

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

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

util_avg_entry 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.

KEEP EXPLORING

More on Delx Mcp A2a, and thousands of servers like it.

This server

All 1076 Delx Mcp A2a tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →