get_incoming_summary
AI agents call get_incoming_summary to retrieve information from Waiaas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description reducing confidence, the naming convention strongly implies this is a data retrieval tool that queries incoming transaction information. In a wallet context, 'incoming' likely refers to deposits or transfers received by the wallet. No evidence suggests this modifies state, executes code, deletes data, or moves funds. It falls clearly into the Read category.
From the tool's definition Tool name 'get_incoming_summary' indicates retrieval of summary information (incoming transfers/transactions). The '_summary' suffix and 'get_' prefix suggest a read operation that queries wallet state without modification.
Documented attack patterns abuse exactly the kind of access get_incoming_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Waiaas, and nothing reaches the server without passing your rules. This is the rule we recommend for get_incoming_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_incoming_summary": {}
}
}get_incoming_summary 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_incoming_summary. It is categorised as a Read tool in the Waiaas MCP Server, which means it retrieves data without modifying state.
Register the Waiaas MCP server in PolicyLayer and add a rule for get_incoming_summary: 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 Waiaas. Nothing to install.
get_incoming_summary 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 get_incoming_summary 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 get_incoming_summary. 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.
get_incoming_summary is provided by the Waiaas MCP server (minhoyoo-iotrust/waiaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Waiaas, 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.
126 Waiaas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.