Get protocol by id
AI agents call api_vestige_view_protocol_by_id to retrieve information from Sperax Ecosystem Crypto & DeFI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple lookup/query operation that retrieves protocol information by identifier. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. The blast radius of misuse is minimal—an agent could only retrieve information that is likely already public.
From the tool's definition Tool name 'api_vestige_view_protocol_by_id' and description 'Get protocol by id' indicate a data retrieval operation. No modification, deletion, execution, or financial transaction is implied.
Documented attack patterns abuse exactly the kind of access api_vestige_view_protocol_by_id gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for api_vestige_view_protocol_by_id:
{
"version": "1",
"default": "deny",
"tools": {
"api_vestige_view_protocol_by_id": {}
}
} api_vestige_view_protocol_by_id is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get protocol by id. It is categorised as a Read tool in the Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for api_vestige_view_protocol_by_id: 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 Sperax Ecosystem Crypto & DeFI MCP Server. Nothing to install.
api_vestige_view_protocol_by_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the api_vestige_view_protocol_by_id 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 api_vestige_view_protocol_by_id. 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.
api_vestige_view_protocol_by_id is provided by the Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sperax Ecosystem Crypto & DeFI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1318 Sperax Ecosystem Crypto & DeFI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.