get_last_error

Get the last error code and description.

SERVERMCP Trader Server SOURCEaf7007/mcp-trader

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/af7007-mcp-trader/get-last-error.md

WHAT IT DOES

What get_last_error does on MCP Trader Server

AI agents call get_last_error to retrieve information from MCP Trader Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_last_error is rated Low

This tool retrieves diagnostic information (error codes and descriptions) from the trading system. It is purely informational—it reads error state without creating, modifying, deleting data, or executing trades. Even in the context of a financial trading server, this specific tool has no capability to move money, execute orders, or make irreversible changes.

From the tool's definition Tool name 'get_last_error' and description 'Get the last error code and description' indicate a retrieval operation with no side effects. It queries error state without modifying system state or triggering actions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_last_error safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Trader Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_last_error, this is the rule to start with:

get_last_error Allowed

get_last_error is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_last_error": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Trader Server, apply this rule, and every get_last_error call is checked against it from then on.

FAQ

Questions about get_last_error

What does the get_last_error tool do? +

Get the last error code and description. It is categorised as a Read tool in the MCP Trader Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_last_error? +

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

What risk level is get_last_error? +

get_last_error is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_last_error? +

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

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

get_last_error is provided by the MCP Trader Server MCP server (af7007/mcp-trader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Trader Server, and thousands of servers like it.

This server

All 45 MCP Trader Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →