High Risk →

strategy.carry.screen

Screens all DeFi lending markets across Aave v3, Compound V3, Fluid, Morpho Blue, and Spark — plus Pendle PT fixed-rate rows — for positive carry, defined as collateral supply APY minus borrow APY. Returns strategies ranked by net carry (highest first), with leveraged carry at 70% of max LTV, est...

Part of the Syenite server.

strategy.carry.screen can trigger actions in Syenite, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SYENITE →

Free to start. No card required.

AI agents invoke strategy.carry.screen to trigger processes or run actions in Syenite. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

strategy.carry.screen can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "strategy.carry.screen": {
      "limits": [
        {
          "counter": "strategy.carry.screen_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Syenite policy for all 46 tools.

Get this rule live on your own Syenite server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SYENITE →

View all 46 tools →

These attack patterns abuse exactly the kind of access strategy.carry.screen 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 strategy.carry.screen only ever does what you allow.

SECURE SYENITE →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the strategy.carry.screen tool do? +

Screens all DeFi lending markets across Aave v3, Compound V3, Fluid, Morpho Blue, and Spark — plus Pendle PT fixed-rate rows — for positive carry, defined as collateral supply APY minus borrow APY. Returns strategies ranked by net carry (highest first), with leveraged carry at 70% of max LTV, estimated annual USD return for a given position size, available liquidity, and utilization. Call this to discover self-funding positions where deposited collateral earns more than the cost to borrow against it; positive-carry count and best strategy are surfaced in the summary field for quick scanning. Optionally pass collateral (e.g. "wstETH"), borrowAsset (default "USDC"), chain, minCarry threshold (e.g. 0.5 for 0.5%+), and positionSizeUSD to size annual return estimates. This tool is read-only; use lending.risk.assess and the lending execute tools to act on a strategy.. It is categorised as a Execute tool in the Syenite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on strategy.carry.screen? +

Register the Syenite MCP server in PolicyLayer and add a rule for strategy.carry.screen: 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 Syenite. Nothing to install.

What risk level is strategy.carry.screen? +

strategy.carry.screen is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit strategy.carry.screen? +

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

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

strategy.carry.screen is provided by the Syenite MCP server (@syenite/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Syenite tool call.

Deterministic rules across all 46 Syenite 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.