AI agents call get_transaction_info to retrieve information from SeldomMaster without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to query or retrieve transaction information without modifying state, moving money, or executing code. It fits the Read category as a data retrieval operation. Severity is low because retrieval operations have minimal blast radius unless they expose highly sensitive data, which is not indicated here.
From the tool's definition Tool name 'get_transaction_info' indicates retrieval of transaction data. The description is minimal ('Name: get_transaction_info') and provides no evidence of write, delete, execute, or financial operations.
Documented attack patterns abuse exactly the kind of access get_transaction_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SeldomMaster, and nothing reaches the server without passing your rules. This is the rule we recommend for get_transaction_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_transaction_info": {}
}
}get_transaction_info 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.
Name: get_transaction_info. It is categorised as a Read tool in the SeldomMaster MCP Server, which means it retrieves data without modifying state.
Register the SeldomMaster MCP server in PolicyLayer and add a rule for get_transaction_info: 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 SeldomMaster. Nothing to install.
get_transaction_info 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_transaction_info 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_transaction_info. 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_transaction_info is provided by the SeldomMaster MCP server (paralax/seldommonster). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SeldomMaster, 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.
52 SeldomMaster tools catalogued and risk-classified — across an index of 43,000+ MCP servers.