Low Risk

check_entry_viability

Before entering a lending position, verify that the market is actually open and has capacity. Checks market status (active, frozen, borrowing enabled), supply/borrow caps, and available liquidity. Returns a clear viable/not-viable verdict. Args: api_key: Your PreFlyte API key (required). protocol...

Risk signalsHandles credentials or secrets (api_key)

Part of the PreFlyte — DeFi Financial Intelligence for AI Agents server.

check_entry_viability is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE PREFLYTE — DEFI FINANCIAL INTELLIGENCE FOR AI AGENTS →

Free to start. No card required.

AI agents call check_entry_viability to retrieve information from PreFlyte — DeFi Financial Intelligence for AI Agents 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 check_entry_viability 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_entry_viability": {}
  }
}

See the full PreFlyte — DeFi Financial Intelligence for AI Agents policy for all 9 tools.

Get this rule live on your own PreFlyte — DeFi Financial Intelligence for AI Agents server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY PREFLYTE — DEFI FINANCIAL INTELLIGENCE FOR AI AGENTS →

View all 9 tools →

These attack patterns abuse exactly the kind of access check_entry_viability gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so check_entry_viability only ever does what you allow.

SECURE PREFLYTE — DEFI FINANCIAL INTELLIGENCE FOR AI AGENTS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the check_entry_viability tool do? +

Before entering a lending position, verify that the market is actually open and has capacity. Checks market status (active, frozen, borrowing enabled), supply/borrow caps, and available liquidity. Returns a clear viable/not-viable verdict. Args: api_key: Your PreFlyte API key (required). protocol: Protocol name — "aave-v3" or "compound-v3". chain: Chain name — "ethereum" or "arbitrum". asset: Asset symbol — "USDC", "WETH", etc. action: "supply" or "borrow". amount_usd: Intended position size in USD (optional, for context). Returns: Dictionary with viable (true/false), market_status, capacity details, current rate, and confidence level.. It is categorised as a Read tool in the PreFlyte — DeFi Financial Intelligence for AI Agents MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_entry_viability? +

Register the PreFlyte — DeFi Financial Intelligence for AI Agents MCP server in PolicyLayer and add a rule for check_entry_viability: 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 PreFlyte — DeFi Financial Intelligence for AI Agents. Nothing to install.

What risk level is check_entry_viability? +

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

Can I rate-limit check_entry_viability? +

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

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

check_entry_viability is provided by the PreFlyte — DeFi Financial Intelligence for AI Agents MCP server (https://mcp.preflyte.xyz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PreFlyte — DeFi Financial Intelligence for AI Agents tool call.

Deterministic rules across all 9 PreFlyte — DeFi Financial Intelligence for AI Agents tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.