SECURITM Launches MCP Server for External AI Access to Security Data
SECURITM has launched an MCP server that allows external AI assistants to query its platform data on assets, risks, tasks, and metrics without manual export.
The company states this is the first MCP server implemented by a Russian SGRC or SOAR vendor. MCP is an open protocol designed to connect AI models to external tools and data sources.
Users can now ask questions such as which critical assets lack owners, which tasks are overdue, or how key indicators changed over the past month. The AI can return tables, executive summaries, or draft work plans, and follow-up queries can refine results by grouping overdue items by assignee.
Supported assistants include GigaChat, Yandex solutions, Claude, ChatGPT, Cursor, and local models with MCP integration. Configuration depends on the chosen tool.
The server operates in read-only mode, preventing any modification of risks or closure of tasks. Connections use separate MCP tokens and can be restricted by IP address.
The capability extends the platform’s existing built-in AI assistant and is available in paid cloud and on-premise versions of SECURITM.
Related articles
HackerSec Launches Pentest Superintelligence Using Orchestrated Frontier AI Models
HackerSec has introduced Pentest Superintelligence, a new offensive cybersecurity methodology that orchestrates multiple high-capacity frontier AI models within a single pentest operation. This builds on the company's earlier Pentest AI-First and Pentest AI-Native approaches by requiring at least two frontier models coordinated through a proprietary runtime. The Yaga autonomous agent serves as the core platform, using a custom harness to integrate models from OpenAI, Anthropic, and xAI while preserving operational context from reconnaissance through exploitation. In internal YagaBench evaluations, the six-model orchestrated setup achieved 98 percent resolution of black-box scenarios compared to 40.5 percent for the best single model. All testing remains within authorized scopes with human oversight for result validation. The development shifts industry focus from merely adding AI to tools toward proving effective multi-model coordination and verifiable impact.
Taming the LLM Dragon: Corporate AI Gateway Architecture Addresses Classic Proxy Shortcomings
Spontaneous adoption of generative AI across enterprises has created shadow AI risks, prompt leaks, and uncontrolled token consumption that standard L7 proxies cannot mitigate. Traditional solutions built on Nginx, Envoy or Kong lack the ability to inspect Server-Sent Events streams, classify sensitive content inside prompts, or enforce token-based quotas in real time. The AI Optimum platform introduces a specialized AI gateway layer that sits between internal consumers and both local inference clusters and external APIs such as GigaChat and YandexGPT. It performs inline PII masking, routes traffic according to data sensitivity, supports OpenAI-compatible endpoints, and maintains detailed audit logs required under 152-FZ. The gateway adds only tens of milliseconds of latency while enabling granular billing, context caching optimization, and protection against runaway agent loops. Subsequent articles in the series will examine real corporate AI spend and further regulatory controls.
Why We Banned Our AI Manager from Writing Code and Assigned the Task to Claude Opus
The team behind an AI-powered marketplace manager for Wildberries initially built the system using regular updates, then migrated it to an autonomous agent. After implementing multiple layers of restrictions, they ultimately removed the agent entirely and rebuilt the solution from scratch. The new architecture relies on a single tool that handles the complete Wildberries API along with internet access while respecting all platform limits. The decision to prohibit the original AI manager from generating code stemmed from concerns over reliability and security in production environments. Instead, the developers turned to Claude Opus to handle coding tasks. This case highlights practical challenges of deploying AI agents in e-commerce automation and information security contexts.
Developer Builds MCP Linter and Discovers Security Issues in Anthropic Official Servers
A developer has released mcp-linter, a lightweight security and compliance tool for the Model Context Protocol used by Anthropic's Claude ecosystem. The linter detects critical problems such as stdout pollution that breaks JSON-RPC framing, missing destructiveHint annotations that allow autonomous agents to execute dangerous actions without human confirmation, prompt injection vectors hidden inside tool descriptions, and incomplete input schemas that increase model hallucinations. When run against Anthropic's reference servers, the tool assigned low health scores to server-memory and especially server-filesystem, highlighting dozens of parameters lacking descriptions. The utility runs with zero dependencies, supports SARIF output for GitHub Security, and can generate automatic JSON patches. The project is open source under MIT license and already integrates into CI pipelines via a dedicated GitHub Action.