Return orders joined with user and product fields for convenient display.
AI agents call order_joined to retrieve information from Database MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays joined data from multiple tables (orders, users, products). The verb 'Return' and the purpose 'for convenient display' confirm it performs a read-only query operation. No creation, modification, deletion, or code execution is involved. It is lower risk than other tools on this server like order_create, order_delete, or order_update.
From the tool's definition Tool name 'order_joined' and description 'Return orders joined with user and product fields for convenient display' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Return orders joined with user and product fields for convenient display. It is categorised as a Read tool in the Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Database MCP Server MCP server in PolicyLayer and add a rule for order_joined: 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 Database MCP Server. Nothing to install.
order_joined 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 order_joined 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 order_joined. 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.
order_joined is provided by the Database MCP Server MCP server (vrushil1/database-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →