get_catalog
Данные справочника по имени.
This record as markdown: /tools/llm-agent-sniffer-integration/get-catalog.md
What get_catalog does on Llm Agent Sniffer Integration
AI agents call get_catalog to retrieve information from Llm Agent Sniffer Integration without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_catalog is rated Low
Even though get_catalog only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_catalog safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Llm Agent Sniffer Integration, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_catalog, this is the rule to start with:
get_catalog is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Llm Agent Sniffer Integration, apply this rule, and every get_catalog call is checked against it from then on.
Questions about get_catalog
Данные справочника по имени. It is categorised as a Read tool in the Llm Agent Sniffer Integration MCP Server, which means it retrieves data without modifying state.
Register the Llm Agent Sniffer Integration MCP server in PolicyLayer and add a rule for get_catalog: 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 Llm Agent Sniffer Integration. Nothing to install.
get_catalog 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_catalog 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_catalog. 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_catalog is provided by the Llm Agent Sniffer Integration MCP server (mobstardos/llm-agent-sniffer-integration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Llm Agent Sniffer Integration, and thousands of servers like it.
This server
Across the catalogue