Get the full record for a single store by its numeric ID. Use after search_stores to retrieve fields not in the search summary (full address, owner profile, contact details). For a list of *products* in that store, call search_products(store_id=…) instead — this tool returns store metadata only. ...
Part of the Partle server.
Free to start. No card required.
AI agents call get_store to retrieve information from Partle without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_store only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_store": {}
}
}See the full Partle policy for all 21 tools.
These attack patterns abuse exactly the kind of access get_store gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get the full record for a single store by its numeric ID. Use after search_stores to retrieve fields not in the search summary (full address, owner profile, contact details). For a list of *products* in that store, call search_products(store_id=…) instead — this tool returns store metadata only. Read-only. No authentication. Args: store_id: Integer id from a search_stores result. Returns: A single store object with all fields. Returns {"error": ...} if the ID does not exist.. It is categorised as a Read tool in the Partle MCP Server, which means it retrieves data without modifying state.
Register the Partle MCP server in PolicyLayer and add a rule for get_store: 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 Partle. Nothing to install.
get_store 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_store 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_store. 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_store is provided by the Partle MCP server (https://partle.rubenayla.xyz/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Partle tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.