Profile wallet behavior against baselines. Send normal wallet transaction patterns as training (tx_count, avg_value, unique_tokens, gas_spent, active_days, etc.) and suspect wallets as test. Detects bot activity, wash trading wallets, and sybil patterns. Example: Profile 50 organic wallets → test...
Part of the WaveGuard server.
Free to start. No card required.
AI agents use waveguard_wallet_profile to create or modify resources in WaveGuard. 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 waveguard_wallet_profile 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 WaveGuard.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"waveguard_wallet_profile": {
"limits": [
{
"counter": "waveguard_wallet_profile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full WaveGuard policy for all 19 tools.
These attack patterns abuse exactly the kind of access waveguard_wallet_profile gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Profile wallet behavior against baselines. Send normal wallet transaction patterns as training (tx_count, avg_value, unique_tokens, gas_spent, active_days, etc.) and suspect wallets as test. Detects bot activity, wash trading wallets, and sybil patterns. Example: Profile 50 organic wallets → test 10 suspect addresses.. It is categorised as a Write tool in the WaveGuard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WaveGuard MCP server in PolicyLayer and add a rule for waveguard_wallet_profile: 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 WaveGuard. Nothing to install.
waveguard_wallet_profile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the waveguard_wallet_profile 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 waveguard_wallet_profile. 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.
waveguard_wallet_profile is provided by the WaveGuard MCP server (https://gpartin--waveguard-api-fastapi-app.modal.run/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 WaveGuard 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.