Persist a user-stated preference, watchlist entry, threshold, or any context that should survive conversation compaction and MCP restart. Examples: 'monitor wallet 0xabc... on Base and Arbitrum', 'ignore stETH HF dips above 1.5', 'alert only when collateral > $10k'. Returns the saved finding with...
Part of the Graph Aave server.
Free to start. No card required.
AI agents invoke note_finding to trigger processes or run actions in Graph Aave. 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.
note_finding 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.
{
"version": "1",
"default": "deny",
"tools": {
"note_finding": {
"limits": [
{
"counter": "note_finding_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Graph Aave policy for all 46 tools.
These attack patterns abuse exactly the kind of access note_finding gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Persist a user-stated preference, watchlist entry, threshold, or any context that should survive conversation compaction and MCP restart. Examples: 'monitor wallet 0xabc... on Base and Arbitrum', 'ignore stETH HF dips above 1.5', 'alert only when collateral > $10k'. Returns the saved finding with an id. Call get_session_state at workflow start to recover saved findings.. It is categorised as a Execute tool in the Graph Aave MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Graph Aave MCP server in PolicyLayer and add a rule for note_finding: 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 Graph Aave. Nothing to install.
note_finding 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 note_finding 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 note_finding. 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.
note_finding is provided by the Graph Aave MCP server (graph-aave-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 46 Graph Aave 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.