Fetch detailed information for a single agent including instructions, knowledge sources, and actions.
AI agents call load_agent_info to retrieve information from Agent 365 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only query to retrieve agent metadata (instructions, knowledge sources, actions). It has no side effects—it does not create, modify, delete, or execute operations. While the fetched data may be sensitive within an M365 context, the tool itself is non-destructive and non-mutating, classifying it as Read with low severity.
From the tool's definition Tool name 'load_agent_info' and description 'Fetch detailed information for a single agent' indicate a data retrieval operation with no modification of state.
Documented attack patterns abuse exactly the kind of access load_agent_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent 365, and nothing reaches the server without passing your rules. This is the rule we recommend for load_agent_info:
{
"version": "1",
"default": "deny",
"tools": {
"load_agent_info": {}
}
}load_agent_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch detailed information for a single agent including instructions, knowledge sources, and actions. It is categorised as a Read tool in the Agent 365 MCP Server, which means it retrieves data without modifying state.
Register the Agent 365 MCP server in PolicyLayer and add a rule for load_agent_info: 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 Agent 365. Nothing to install.
load_agent_info 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 load_agent_info 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 load_agent_info. 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.
load_agent_info is provided by the Agent 365 MCP server (ramakrishnan24689/agent365-mcpapp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent 365, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Agent 365 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.