search-audits

Search Descope project audit logs

SERVERDescope MCP Server SOURCEdescope-sample-apps/descope-mcp-server-stdio

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/descope-sample-apps-descope-mcp-server/search-audits.md

WHAT IT DOES

What search-audits does on Descope MCP Server

AI agents call search-audits to retrieve information from Descope MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why search-audits is rated Low

This tool queries and retrieves audit log information without creating, modifying, deleting, or executing any operations. It is a read-only operation that has no side effects on the system or data. The low severity reflects minimal blast radius—an AI agent misusing this tool could only over-query or access audit logs, not cause irreversible harm or execute arbitrary operations.

From the tool's definition Tool name 'search-audits' and description 'Search Descope project audit logs' indicate retrieval of audit log data with no modification or deletion of records.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search-audits safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Descope MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search-audits, this is the rule to start with:

search-audits Allowed

search-audits is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search-audits": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Descope MCP Server, apply this rule, and every search-audits call is checked against it from then on.

FAQ

Questions about search-audits

What does the search-audits tool do? +

Search Descope project audit logs. It is categorised as a Read tool in the Descope MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search-audits? +

Register the Descope MCP Server MCP server in PolicyLayer and add a rule for search-audits: 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 Descope MCP Server. Nothing to install.

What risk level is search-audits? +

search-audits is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search-audits? +

Yes. Add a rate_limit block to the search-audits 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.

How do I block search-audits completely? +

Set action: deny in the PolicyLayer policy for search-audits. 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.

What MCP server provides search-audits? +

search-audits is provided by the Descope MCP Server MCP server (descope-sample-apps/descope-mcp-server-stdio). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Descope MCP Server, and thousands of servers like it.

This server

All 4 Descope MCP Server tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →