get_period_context
AI agents call get_period_context to retrieve information from Adaptive Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates a GET operation, which retrieves period-specific context. With an empty description and only the name to judge, it most likely retrieves or queries context data with no side effects. However, confidence is lowered to 0.6 due to lack of explicit documentation. If the tool unexpectedly modifies state or executes code, this classification may need revision.
From the tool's definition Tool name 'get_period_context' implies retrieval of contextual information for a time period; no modification or execution indicated by the name. Description is empty, reducing confidence.
Attacks that exploit this kind of access
get_period_context. It is categorised as a Read tool in the Adaptive Agent MCP Server, which means it retrieves data without modifying state.
Register the Adaptive Agent MCP server in PolicyLayer and add a rule for get_period_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 Adaptive Agent. Nothing to install.
get_period_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_period_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_period_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_period_context is provided by the Adaptive Agent MCP server (justforever17/adaptive-agent-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 →