AI agents call get_semantic_context to retrieve information from Querywise without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve semantic metadata (glossary, metrics, data dictionary context) from the embedded SQLite store. No description is provided, which slightly lowers confidence, but the read-only design of the system and the tool's name strongly suggest it queries/retrieves semantic information without side effects. No delete, write, execute, or financial operations are implied.
From the tool's definition Tool name 'get_semantic_context' combined with server description stating 'read-only by default' and semantic layer for querying. Sibling tools like 'describe_table' and 'add_glossary_term' indicate this retrieves metadata/context rather than modifying data.
Attacks that exploit this kind of access
get_semantic_context. It is categorised as a Read tool in the Querywise MCP Server, which means it retrieves data without modifying state.
Register the Querywise MCP server in PolicyLayer and add a rule for get_semantic_context: 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 Querywise. Nothing to install.
get_semantic_context 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_semantic_context 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_semantic_context. 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_semantic_context is provided by the Querywise MCP server (kosminus/querywise-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 →