Skip to main content
Glama
Shrike-Security

Shrike Security MCP Server

scan_web_search

Read-onlyIdempotent

Scan web search queries to prevent PII leaks and data exfiltration. Blocks queries containing sensitive data or suspicious targets before they reach external search engines.

Instructions

Protective check on web search queries — catches PII leaks or suspicious targets before queries reach external services, so internal data doesn't escape through a search bar.

Call this BEFORE executing any web search query on behalf of a user or agent.

DECISION LOGIC:

  • If blocked=true: do NOT execute the search. Return the user_message explaining the query was rejected.

  • If blocked=false: the search query is safe to execute.

Checks for:

  • PII in search queries (SSN, credit cards, API keys, private keys)

  • Data exfiltration patterns (searching for leaked credentials, Google dorks)

  • Blocked/suspicious domains (paste sites, suspicious TLDs)

Enterprise context: Prevents agents from inadvertently leaking internal data (names, account numbers, internal project names) through external search engines.

ERROR HANDLING: If this tool returns an error or is unavailable, default to BLOCKING the search. Do NOT send unscanned queries to external services.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query to scan
targetDomainsNoOptional list of target domains to validate
session_idNoSession identifier for multi-turn correlation.
agent_idNoYour agent identifier for activity tracking.
parent_agent_idNoParent agent ID if you are a sub-agent (delegation chain tracking).
task_chainNoDelegation path from root agent (e.g., "main→research→fetch").
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations (readOnlyHint, destructiveHint, idempotentHint) are consistent with a safe scanning operation. The description adds behavioral details about checking for PII, data exfiltration, and blocked domains, plus error-handling behavior, enhancing transparency beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (purpose, when to use, decision logic, checks, enterprise context, error handling). It is concise, front-loaded with the critical action, and every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description adequately explains the return value behavior (blocked boolean) and decision logic. It covers error handling and enterprise context. Minor omission: does not detail what happens with targetDomains parameter, but overall complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with all parameters described. The description reinforces the purpose of the query parameter and mentions targetDomains implicitly, but does not add significant new meaning beyond the schema definitions. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as a protective scan for web search queries to catch PII and suspicious targets. It distinguishes itself from sibling scan tools (e.g., scan_prompt, scan_sql_query) by focusing specifically on web search queries, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'Call this BEFORE executing any web search query' and provides decision logic for when to block or allow the query. It also includes error-handling fallback to block. While no alternative tools are mentioned, the guidelines are clear and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Shrike-Security/shrike-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server