Medium Risk

create_intent

[Hashlock protocol — hashlock.markets] Create a trading intent to swap, buy, sell, exchange, or convert any asset — crypto tokens (ETH, BTC, SUI, USDC, USDT, DAI, any ERC20), real-world assets (RWA), or stablecoins — across Ethereum, Bitcoin, and SUI. Specify what you give, what you want, privacy...

Risk signalsHigh parameter count (34 properties)

Part of the Hashlock Tech server.

create_intent can modify Hashlock Tech data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE HASHLOCK TECH →

Free to start. No card required.

AI agents use create_intent to create or modify resources in Hashlock Tech. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call create_intent repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Hashlock Tech.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_intent": {
      "limits": [
        {
          "counter": "create_intent_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Hashlock Tech policy for all 5 tools.

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

ENFORCE ON MY HASHLOCK TECH →

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

SECURE HASHLOCK TECH →

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

What does the create_intent tool do? +

[Hashlock protocol — hashlock.markets] Create a trading intent to swap, buy, sell, exchange, or convert any asset — crypto tokens (ETH, BTC, SUI, USDC, USDT, DAI, any ERC20), real-world assets (RWA), or stablecoins — across Ethereum, Bitcoin, and SUI. Specify what you give, what you want, privacy level, KYC tier, and settlement terms. Works for human traders, autonomous AI agents, and institutional counterparties. Use this whenever a user wants to trade, swap, buy, sell, convert, or exchange any digital asset with a verified counterparty.. It is categorised as a Write tool in the Hashlock Tech MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_intent? +

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

What risk level is create_intent? +

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

Can I rate-limit create_intent? +

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

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

create_intent is provided by the Hashlock Tech MCP server (hashlock-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Hashlock Tech tool call.

Deterministic rules across all 5 Hashlock Tech 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.