Search conferences by keyword.
AI agents call search_conferences to retrieve information from Local Tech Digest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or filters conference data based on search criteria. It performs a read-only lookup operation with no side effects, data modification, or external command execution. The keyword search is a standard information retrieval pattern. Severity is low because misuse would only expose conference information the user likely has authorized access to already.
From the tool's definition Tool name 'search_conferences' and description 'Search conferences by keyword' indicate a query/search operation with no modification or execution of external systems.
Attacks that exploit this kind of access
Search conferences by keyword. It is categorised as a Read tool in the Local Tech Digest MCP Server, which means it retrieves data without modifying state.
Register the Local Tech Digest MCP server in PolicyLayer and add a rule for search_conferences: 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 Local Tech Digest. Nothing to install.
search_conferences 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 search_conferences 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 search_conferences. 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.
search_conferences is provided by the Local Tech Digest MCP server (nk1947-sudo/local-tech-digest-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 →