Skip to main content
Glama

ChainGuard Vault — Solana Rent & 8-Chain EVM Dust Recovery

check_frontend_hijack

Inspect a DeFi frontend URL & optional EIP-1967 proxy contract for missing CSP/SRI, malicious 3rd-party JS, or unauthorized proxy upgrades.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "check_frontend_hijack"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
proxyNo
networkNobase

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full behavioral burden. It usefully discloses the classes of finding it reports, but says nothing about whether it fetches the URL live, whether the call is read-only, what it does when the proxy argument is empty, or how results are shaped.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tightly packed sentence, front-loaded with the verb and target and with zero redundant wording. Every clause adds a distinct check or constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There are no annotations and no output schema, so the description must stand alone; it covers the input targets and the types of findings but omits one parameter's meaning and all operational details (side effects, error behavior, result shape). It is adequate but leaves clear gaps for a security-inspection tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It does explain 'url' (a DeFi frontend) and 'proxy' (EIP-1967, optional), but the third parameter 'network' (default 'base') is never mentioned, leaving a real gap for a 3-parameter tool with no schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Inspect') and concrete resources ('DeFi frontend URL', 'optional EIP-1967 proxy contract'), then enumerates the defects it looks for (missing CSP/SRI, malicious 3rd-party JS, unauthorized proxy upgrades). That is enough to distinguish it from the security-focused siblings (EIP-7702, MCP poisoning, Solana token2022), though it never differentiates itself explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the scenario: you call it when auditing a DeFi frontend or a proxy's upgrade authority. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling tool, and no statement of prerequisites such as the target needing to be reachable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources