AI agents call get_transactions to retrieve information from Shopify Partner Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly indicates a read operation that retrieves transaction data for analytics purposes. The confidence is 0.7 rather than higher because the tool description is empty; if it actually allows filtering/querying arbitrary transaction data or executing complex analytics, it could warrant Execute classification, but based on naming convention and server context, simple data retrieval is most likely.
From the tool's definition Tool name 'get_transactions' combined with the server's stated purpose of 'revenue analytics' and 'retention cohorts' indicates data retrieval. Sibling tools (get_app_details, get_churn_analysis, get_customer_ltv) are all query/read operations.
Documented attack patterns abuse exactly the kind of access get_transactions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Shopify Partner Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for get_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"get_transactions": {}
}
}get_transactions 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_transactions. It is categorised as a Read tool in the Shopify Partner Agent MCP Server, which means it retrieves data without modifying state.
Register the Shopify Partner Agent MCP server in PolicyLayer and add a rule for get_transactions: 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 Shopify Partner Agent. Nothing to install.
get_transactions 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_transactions 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_transactions. 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_transactions is provided by the Shopify Partner Agent MCP server (rushikeshmore/shopify-partner-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Shopify Partner Agent, 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.
25 Shopify Partner Agent tools catalogued and risk-classified — across an index of 43,000+ MCP servers.