获取医学会议记录的详细信息
AI agents call get_meeting to retrieve information from KnowS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries meeting records from a medical evidence database. There are no indications of creation, modification, deletion, code execution, or financial operations. The blast radius of misuse is minimal—an agent could retrieve sensitive meeting information but cannot alter, execute commands, or cause irreversible damage. This is a straightforward read/query operation.
From the tool's definition Tool name 'get_meeting' and description '获取医学会议记录的详细信息' (retrieve detailed information of medical meeting records) indicate a retrieval operation. The verb '获取' (get/retrieve) and context of fetching meeting record details without modification capabilities.
Attacks that exploit this kind of access
获取医学会议记录的详细信息. It is categorised as a Read tool in the KnowS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KnowS MCP Server MCP server in PolicyLayer and add a rule for get_meeting: 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 KnowS MCP Server. Nothing to install.
get_meeting 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_meeting 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_meeting. 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_meeting is provided by the KnowS MCP Server MCP server (pancrepal-xiaoyibao/mcp-knows-ai). 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 →